[PATCH 2/3] avoid hardcoded use of gpg2 in gpgcompose documentation

Werner Koch wk at gnupg.org
Tue Apr 5 11:22:55 CEST 2016

On Wed, 30 Mar 2016 17:51, dkg at fifthhorseman.net said:
> * g10/gpgcompose.c: use GPG_NAME configure variable instead of
>   hardcoded string "gpg2" in example output.

I have done this as part of 7b58a11f.  However, I also changed the build
system to build gpgcompose when configure has been run with
--enable-maintainer-mode.  The reason for this is that gpgcompose
diverts in some details too much from the other tools and thus I fear
that we will run into portability problems.  This should also be an
indication that gpgcompose may change at any time without notice.



Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.

More information about the Gnupg-devel mailing list