From: ludo@gnu.org (Ludovic Courtès)
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme, and pinentry
Date: Thu, 20 Feb 2014 15:18:38 +0100 [thread overview]
Message-ID: <87fvnd7tq9.fsf@gnu.org> (raw)
In-Reply-To: <8761oa8o17.fsf@netris.org> (Mark H. Weaver's message of "Wed, 19 Feb 2014 22:24:04 -0500")
Mark H Weaver <mhw@netris.org> skribis:
> ludo@gnu.org (Ludovic Courtès) writes:
>
>> Mark H Weaver <mhw@netris.org> skribis:
>>
>>> From e6ddaf74f30ee5d6c8d76a3ae9cacdb14eb060c5 Mon Sep 17 00:00:00 2001
>>> From: Mark H Weaver <mhw@netris.org>
>>> 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 <mhw@netris.org>
> 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’.
prev parent reply other threads:[~2014-02-20 14:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:31 [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme, and pinentry Mark H Weaver
2014-02-19 13:43 ` Ludovic Courtès
2014-02-20 3:24 ` Mark H Weaver
2014-02-20 14:18 ` Ludovic Courtès [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87fvnd7tq9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).