installing gnupg 2.2 as "gpg", vs coexistence with gpg 1.4

[Greg Troxel]

Thanks to everyone for the replies and discussion.

From my packaging viewpoint, the ideal situation would be if there is a
gnupg 1.4.x release which installs to gpg1 (and really, does not install
any files which conflict with gnupg 2.2.x).   Then I could upgrade that,
flip off the gpg2 switch on 2.2.x, and make anything that depends on 1.4
change to 2.2, and then pick up the pieces from ununderstood
consequences.

Plan B would be just the rest of the steps, leading to people not being
able to install 1.4.x.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 162 bytes
Desc: not available
URL: </pipermail/attachments/20171009/184b101e/attachment.sig>