From: Mark H Weaver <mhw@netris.org>
To: guix-devel@gnu.org
Subject: [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme, and pinentry
Date: Wed, 19 Feb 2014 05:31:24 -0500 [thread overview]
Message-ID: <87k3cr8kcj.fsf@netris.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 201 bytes --]
This patch is actually a prerequisite to the "Add gmime" patch. I could
have added 'libgpg-error' as another input to 'gmime', but this seemed
the more proper solution.
What do you think?
Mark
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme, and pinentry --]
[-- Type: text/x-patch, Size: 2052 bytes --]
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.
---
gnu/packages/gnupg.scm | 10 +++++++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/gnupg.scm b/gnu/packages/gnupg.scm
index 499b200..cadcda8 100644
--- a/gnu/packages/gnupg.scm
+++ b/gnu/packages/gnupg.scm
@@ -181,12 +181,13 @@ specifications are building blocks of S/MIME and TLS.")
(base32
"0lg210acj2rxq291q4cwamg9gx6gh2prb1xa93y5jhw5b6r0lza3"))))
(build-system gnu-build-system)
+ (propagated-inputs
+ `(("libgpg-error" ,libgpg-error)))
(inputs
`(("bzip2" ,guix:bzip2)
("curl" ,curl)
("libassuan" ,libassuan)
("libgcrypt" ,libgcrypt)
- ("libgpg-error" ,libgpg-error)
("libksba" ,libksba)
("pth" ,pth)
("openldap" ,openldap)
@@ -226,10 +227,11 @@ components), libgpg-error (centralized GnuPG error values), and libskba
(base32
"15h429h6pd67iiv580bjmwbkadpxsdppw0xrqpcm4dvm24jc271d"))))
(build-system gnu-build-system)
+ (propagated-inputs
+ `(("libgpg-error" ,libgpg-error)))
(inputs
`(("gnupg" ,gnupg)
- ("libassuan" ,libassuan)
- ("libgpg-error" ,libgpg-error)))
+ ("libassuan" ,libassuan)))
(home-page "http://www.gnupg.org/related_software/gpgme/")
(synopsis "library providing simplified access to GnuPG functionality")
(description
@@ -411,6 +413,8 @@ including tools for signing keys, keyring analysis, and party preparation.
(base32
"1bd047crf7xb8g61mval8v6qww98rddlsw2dz6j8h8qbnl4hp2sn"))))
(build-system gnu-build-system)
+ (propagated-inputs
+ `(("libgpg-error" ,libgpg-error)))
(inputs
`(("ncurses" ,ncurses)
("gtk+" ,gtk+-2)
--
1.8.4
next reply other threads:[~2014-02-19 10:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-19 10:31 Mark H Weaver [this message]
2014-02-19 13:43 ` [PATCH] gnu: Add libgpg-error as propagated inputs to gnupg, gpgme, and pinentry Ludovic Courtès
2014-02-20 3:24 ` Mark H Weaver
2014-02-20 14:18 ` Ludovic Courtès
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=87k3cr8kcj.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.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).