GPG_NAME vs. --gpg2-is-gpg vs. documentation vs. installation

[Werner Koch]

On Wed, 30 Mar 2016 16:53, dkg at fifthhorseman.net said:

> configure.ac defines a GPG_NAME variable that determines what we call
> gpg.  it also offers a --gpg2-is-gpg option, which sets the config

GPG_NAME allow to re-brand GnuPG.  Here it is not due to trademark
problems but simply because I had a customer who wanted GnUPG but under
a different name.  Thus I generalized this.

I can't remember the origin of --gpg2-is-gpg option but it was either due
to our old and unmaintained port to WindowsCE 3.5 or for Windows.

> In addition to this, much of the documentation hard-codes "gpg2" or
> "gpgv2", as do some embedded strings and help messages.

Ooops.

> once at ./configure time (--gpg2-is-gpg seems like a good place for

That is probably the easiest to do.

> Any thoughts about making this sort of change?  I can supply a few
> patches in this direction that should improve things, but i don't know

Yes, it should indeed be done.  Given that I did all the work for
re-branding it is likely easier if I go and fix that.


Shalom-Salam,

   Werner

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