[arch-dev-public] Upgrading gnupg to 2.0 branch, removing gnupg2

Allan McRae allan at archlinux.org
Sun Mar 18 18:20:34 EDT 2012

On 18/03/12 22:08, Tom Gundersen wrote:
> On Sun, Mar 18, 2012 at 8:00 AM, Allan McRae <allan at archlinux.org> wrote:
>> Now...  has anyone proposing this actually done the work and noted which
>> configure options get disabled when building gpgme against only one of
>> gnupg or gnupg2.  I remember there was differences when I was looking
>> into this for the same request made back in 2010
>> (https://bugs.archlinux.org/task/22110).  I can not remember the
>> results, but I remember there was a difference.
> I tried building it only against gnupg2, and as far as I could tell it
> made no difference. If I understood correctly building against gnupg1
> means that we don't get support for gpgms (at least).
> Dropping gnupg2 does not sound like a good idea, as that means people
> would have to build a second verision of gpgme to get gnupg2 features.

I believe you can use make/optdepends there...

> Furthermore, if we drop gnupg1, we could eventually drop it from the
> repos all together, which would not be the case for gnup2 as it has
> more features people might need.

I think thet gnupg1 is more suited to what _ALL_ Arch systems use gpgme
for.  The simple verification of package signatures.


More information about the arch-dev-public mailing list