[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme,
|
From: |
Ludovic Courtès |
|
Subject: |
Re: [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme, and pinentry |
|
Date: |
Wed, 19 Feb 2014 14:43:59 +0100 |
|
User-agent: |
Gnus/5.130007 (Ma Gnus v0.7) Emacs/24.3 (gnu/linux) |
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?
Also, please write a one-line rationale for the propagation as a
comment.
Thanks,
Ludo’.