You are right, the installation of the gnupg 2 line of code (gnupg-1.9 will eventually end up as gnupg 2) is not as easy as the standard gpg. One problem seems to be that I have been pretty conservative and flagged the gnupg 1.9 branch as "experimental". This is not really the truth but more a consession for the 1.2 branch (tagged "stable") and the 1.3 branch (tagged "development"). A suggestion for a better tag is welcome.
gnupg 1.9 is really usable and part of the EPROSS release done by the German BSI (they need the S/MIME part of it). One thing which is not yet really stable is the gpg part (i.e. the classic OpenPGP) of gnupg-1.9 - however it gets installed as gpg2 and will peacefully coexists with any other gpg.
Even old gpgs (1.2.4 or 1.3.6) can make use of the gpg-agent. Given the problems people have with it, today I added a new configure option to allow building just the agent. I hope this will make it easier for distributions to package just gpg-agent so that all gpg aware tools can make use of the passphrase caching and don't need to care about the passphrase dialog at all.
I am convinced that the recent work done at the CVS Kmail will result in an outstanding support for PGP/MIME, that old inline PGP and S/MIME.
Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds