Re: [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme, and pinentry

[Ludovic Courtès]

Mark H Weaver <address@hidden> skribis:

> address@hidden (Ludovic Courtès) writes:
>
>> Mark H Weaver <address@hidden> skribis:
>>
>>> From e6ddaf74f30ee5d6c8d76a3ae9cacdb14eb060c5 Mon Sep 17 00:00:00 2001
>>> From: Mark H Weaver <address@hidden>
>>> Date: Tue, 18 Feb 2014 22:06:34 -0500
>>> Subject: [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg,
>>>  gpgme, and pinentry.
>>>
>>> * gnu/packages/gnupg.scm (gnupg, gpgme, pinentry): Make 'libgpg-error'
>>>   a propagated input.
>>
>> This makes sense for GPGME, because it’s a library and its headers may
>> refer to the libgpg-error headers.
>>
>> But what about GnuPG and Pinentry?  These are normally just end-user
>> programs, right?
>
> Indeed, my mistake.

OK.

> From 68640c3c09c6c9ddcaae8d50754f0876b273d42a Mon Sep 17 00:00:00 2001
> From: Mark H Weaver <address@hidden>
> Date: Wed, 19 Feb 2014 19:20:53 -0500
> Subject: [PATCH] gnu: gpgme: Make 'libgpg-error' a propagated input.
>
> * gnu/packages/gnupg.scm (gpgme): Make 'libgpg-error' a propagated input.

OK to push.

Thanks!
Ludo’.