[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gnupg-devel
Subject:    Re: [PATCH 2/3] avoid hardcoded use of gpg2 in gpgcompose documentation
From:       Werner Koch <wk () gnupg ! org>
Date:       2016-04-05 9:22:55
Message-ID: 878u0s2yvk.fsf () wheatstone ! g10code ! de
[Download RAW message or body]

On Wed, 30 Mar 2016 17:51, dkg@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.


Shalom-Salam,

   Werner

-- 
Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.


_______________________________________________
Gnupg-devel mailing list
Gnupg-devel@gnupg.org
http://lists.gnupg.org/mailman/listinfo/gnupg-devel
[prev in list] [next in list] [prev in thread] [next in thread]