gpgme: need *both* gnupg and gnupg2?

[Marcus Brinkmann]

At Tue, 04 Mar 2008 10:16:41 -0600,
Rex Dieter <rdieter at math.unl.edu> wrote:
> 
> Marcus Brinkmann wrote:
> > At Tue, 04 Mar 2008 09:03:18 -0600,
> > Rex Dieter <rdieter at math.unl.edu> wrote:
> >> Rex Dieter wrote:
> >>
> >>> gpgme seems to need both gnupg(1) (for OpenPGP support) and gnupg(2) (for
> >>> CMS support), according to the README.
> >>>
> >>> Can gpg2 be used instead for gpgme's OpenPGP support (using something
> >>> like ./configure --with-gpg=/usr/bin/gpg2) to reduce it's external
> >>> dependencies to just gnupg2?
> >>>
> >>> I naively tried this, and some of the tests performed by 'make check' now
> >>> fail.
> >> Followup, it was part of the regular build (not just 'make check') that
> >> failed, in tests/gpg:
> >> $(GPG) --homedir . --allow-secret-key-import
> >> since gpg2 doesn't support --allow-secret-key-import
> > 
> > Hu?  Which version of gpg2, and what was the error message?
> 
> gnupg-2.0.8,
> 
> /usr/bin/gpg2 --homedir . --allow-secret-key-import \
>                  --import Alpha/Secret.gpg Zulu/Secret.gpg
> gpg: WARNING: unsafe permissions on homedir `.'
> gpg: importing secret keys not allowed
> gpg: importing secret keys not allowed
> gpg: Total number processed: 2
> gpg:       secret keys read: 2
> make[3]: *** [pubring.gpg] Error 2

This is due to --enable-selinux-support, which is off by default, and
seems unrelated to gpg 1 vs 2.  (I didn't test it, though).

Thanks,
Marcus