[gpgme][Feature Request] indicate option to gpgme_op_import*

jbar jeanjacquesbrucker at gmail.com
Fri Sep 21 17:31:59 CEST 2012

 You means that gpgme will use the gpg.conf of its context homedir,
and so that I just need to add such line to that file ? :
 | import-options import-clean 

Thanks a lot, gonna try it with gpgme.

Note: whith gpg 1.4.12 or 2.0.18 the import-clean option works on --import,
      but not on --recv-keys. It is not annoying for me, but what is please
      exactly the reason ?

jbar <jeanjacquesbrucker at gmail.com>

On Fri, 21 Sep 2012 15:33:57 +0200
Werner Koch <wk at gnupg.org> wrote:

> On Fri, 21 Sep 2012 14:46, jeanjacquesbrucker at gmail.com said:
> > I would like to try making a patch, but even with cscope, I didn't
> > have found the real code used in the engine when a gpgme_op_import* is
> > called. (:-/)
> The command is build using the add_arg() functions in engine-gpg.c which
> are finally used by the start() function.  styart() is then called by
> gpg_import().
> > We really need to clean keys in our program (eg "ludd node", and we will also need to minimalize some keys in the futur).
> > But today the only solution I see is to make an ulgy system("gpg ...")
> > call. :
> You may simply provide a different configuration file by setting a
> another homedir with a specialized configuraion file with
> gpgme_set_engine_info.
> Shalom-Salam,
>    Werner
> -- 
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: </pipermail/attachments/20120921/a9e75ebc/attachment.pgp>

More information about the Gnupg-devel mailing list