On Mon, Mar 13, 2017 at 12:14:17PM +0100, Bernhard E. Reiter wrote:
> Using a completely different OpenPGP implementation maybe a potential use case
> for keeping a configuration option around. I did not deeply examine what git
> really needs. Usually a different implementation will have quite a different
> command line interface, so it may require substaintial work to come up with a
> wrapper about that other OpenPGP implementation to provide the same command
> line interface as GnuPG.
The existing config option will have to stay, period. If we take it
away, then we'd be breaking existing setups that do anything more exotic
than point it at a particular gpg binary.
So I think the possible patches in this area are:
- adding gpgme support (probably as an optional build-time dependency)
along with a config option to use it instead of gpg.program (or
possibly just "gpg.program = gpgme" to trigger it).
- defaulting to gpgme (when it's compiled in) instead of gpg.program
The first one by itself shouldn't hurt anybody, aside from carrying some
extra code around.
We'd have to see how the first one goes before considering the second.
If we hit a point where people have problems and the advice is "just set
gpg.program to gpgme", then that's a good sign that the default should
be flipped.
-Peff