[PATCH] GPGME: Always use --runtime for gpgconf changes

Andre Heinecke aheinecke at intevation.de
Mon Jan 2 13:17:57 CET 2017


If a tool uses GPGME for changing configuration values it
needs a way to ensure that these changes take effect. Otherwise
users may change and see config values and do not understand
why they are not working.

Kleopatra did this in the past but since switching to GPGME based gpgconf API,
adding an additional --runtime is no longer possible.

Instead of an Option for this I think --runtime should always be called as I 
can't think of a usecase where a GPGME user would want to change a 
configuration value and not have that change take effect immediately.


Andre Heinecke |  ++49-541-335083-262  | http://www.intevation.de/
Intevation GmbH, Neuer Graben 17, 49074 Osnabrück | AG Osnabrück, HR B 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-core-Always-use-runtime-for-gpgconf-changes.patch
Type: text/x-patch
Size: 968 bytes
Desc: not available
URL: </pipermail/attachments/20170102/57e1b7fe/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: </pipermail/attachments/20170102/57e1b7fe/attachment-0001.sig>

More information about the Gnupg-devel mailing list