Hi, I have noticed recently "app-crypt/gpgme-*" ebuilds were updated to depend on the ">=app-crypt/gnupg-2" to avoid test failures during the build. However, the gpgme can be built and runs perfectly fine with =app-crypt/gnupg-1.4.21 if one passes "--disable-gpgsm-test" to the configure script. Please, if possible, make the dependency of this ebuild on the gnupg less strict. Reproducible: Always
Created attachment 517838 [details, diff] ugly patch to make gpgme build with =app-crypt/gnupg-1.4.21 E.g. attached an ugly patch that allows =app-crypt/gpgme-1.10.0 to be built with =app-crypt/gnupg-1.4.21. (just an example, I do not mean it for production)
all support libraries used by gpgme are of gnupg-2, the test failure shows that upstream does not actually support this setup. regardless, gnupg-1.4 will be removed soon from tree.
