GPG_NAME vs. --gpg2-is-gpg vs. documentation vs. installation
wk at gnupg.org
Tue Apr 5 11:29:41 CEST 2016
On Wed, 30 Mar 2016 17:58, dkg at fifthhorseman.net said:
> Thanks! I've just sent a series of three patches that start down this
Thanks. However, I took a different approach which should yield the same
result. Now GnuPg builds binaries gpg and gpgv and onlys installs them
as gpg2/gpgv2. This has the advantage that eventually we can make
--enable-gpg2-is-gpg the default without chnaging anything else in the
source (e.g. the tests). Thus in the gnupg build tree gpg is now always
> Ideally, they would affect the names and the content of the generated
> manpages and info documentation as well -- for the experimental debian
Will come soon.
> try to produce a similar approach for the "classic" branch: something
> like ./configure --enable-gpg1-is-gpg (it would default to "yes" for
Yep. In this case I would suggest to rename gpg.c to gpg1.c and use
your install-hook to rename gpg1 to gpg in the target directory. We
also need to rename the man page.
> Does that seem like a sensible approach?
Die Gedanken sind frei. Ausnahmen regelt ein Bundesgesetz.
More information about the Gnupg-devel