GnuPG ME: How do we use the --keyring GnuPG option via GnuPG ME?

[mconahan at iotest.org]

Werner Koch wrote:

>On Tue, 08 Feb 2005 14:16:34 -0500, mconahan at iotest org said:
>
>  
>
>>On second thought, is it possible to specify an unique "gpg.conf" file
>>for each gpg session?  If this could work, this would be a
>>    
>>
>
>You won't be able to do that. With a future version you will be able
>to specify a home directory and thus also another gpg.conf:
>
>Noteworthy changes in version 1.1.0 (unreleased)
>------------------------------------------------
>
> * You can now configure the backend engine file name and home
>   directory to be used, as default and per context.
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>gpgme_set_engine_info		NEW
>gpgme_ctx_get_engine_info	NEW
>gpgme_ctx_set_engine_info	NEW
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>
>Salam-Shalom,
>
>   Werner
>
>
>  
>
Doh!

Hmmm... For GPGME 'out of the box', is there a way to utilize the GnuPG 
options "--homedir", "--keyring", "--no-default-keyring", and 
"--secret-keyring" for a context (at a minmum I need the use of the 
latter three)?

If there is not a way 'out of the box', where in the GPGME source would 
I have to add the above GnuPG arguments, in order to have them sent to 
GnuPG along with the rest of the arguments already specified in the 
context? Would it be the function "build_argv" in rungpg.c?