From: David Thompson <dthompson2@worcester.edu>
To: guix-devel@gnu.org
Subject: [PATCHES] Propagate inputs for libxml2 and libxslt
Date: Sat, 28 Feb 2015 10:28:35 -0500 [thread overview]
Message-ID: <87zj7y6onw.fsf@fsf.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 359 bytes --]
Two small patches below for propagating the necessary inputs for libxml2
and libxslt. These should probably be applied to core-updates, right?
Notably, these patches triggers a rebuild of subversion.
Once these patches are applied, would it be a good idea to go through
the packages that depend on libxml2 and libxslt and remove the now
propagated inputs?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-libxml2-Propagate-zlib.patch --]
[-- Type: text/x-diff, Size: 938 bytes --]
From a86da0014e02aa73b1e7554edc9c0cd580608c9d Mon Sep 17 00:00:00 2001
From: David Thompson <dthompson2@worcester.edu>
Date: Fri, 27 Feb 2015 16:59:37 -0500
Subject: [PATCH 1/2] gnu: libxml2: Propagate zlib.
* gnu/packages/xml.scm (libxml2): Propagate zlib input.
---
gnu/packages/xml.scm | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/gnu/packages/xml.scm b/gnu/packages/xml.scm
index f2b3baa..ae2227f 100644
--- a/gnu/packages/xml.scm
+++ b/gnu/packages/xml.scm
@@ -65,7 +65,8 @@ things the parser might find in the XML document (like start tags).")
(build-system gnu-build-system)
(home-page "http://www.xmlsoft.org/")
(synopsis "C parser for XML")
- (inputs `(("zlib" ,zlib)))
+ (propagated-inputs
+ `(("zlib" ,zlib))) ;; -lz is in the .pc file
(native-inputs `(("perl" ,perl)
("python" ,python-2))) ; incompatible with Python 3 (print syntax)
--
2.1.4
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: 0002-gnu-libxslt-Propagate-libxml2.patch --]
[-- Type: text/x-diff, Size: 1168 bytes --]
From 44675222f65f3e539dd66ff604ab97f0ef3c55de Mon Sep 17 00:00:00 2001
From: David Thompson <dthompson2@worcester.edu>
Date: Fri, 27 Feb 2015 21:12:20 -0500
Subject: [PATCH 2/2] gnu: libxslt: Propagate libxml2.
* gnu/packages/xml.scm (libxslt): Propagate libxml2.
---
gnu/packages/xml.scm | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/xml.scm b/gnu/packages/xml.scm
index ae2227f..675a3ff 100644
--- a/gnu/packages/xml.scm
+++ b/gnu/packages/xml.scm
@@ -118,9 +118,9 @@ things the parser might find in the XML document (like start tags).")
(home-page "http://xmlsoft.org/XSLT/index.html")
(synopsis "C library for applying XSLT stylesheets to XML documents")
(inputs `(("libgcrypt" ,libgcrypt)
- ("libxml2" ,libxml2)
- ("python" ,python-wrapper)
- ("zlib" ,zlib)))
+ ("python" ,python-wrapper)))
+ (propagated-inputs
+ `(("libxml2" ,libxml2))) ;; -lxml2 is in the .pc file
(description
"Libxslt is an XSLT C library developed for the GNOME project. It is
based on libxml for XML parsing, tree manipulation and XPath support.")
--
2.1.4
[-- Attachment #4: Type: text/plain, Size: 136 bytes --]
--
David Thompson
Web Developer - Free Software Foundation - http://fsf.org
GPG Key: 0FF1D807
Support the FSF: https://fsf.org/donate
next reply other threads:[~2015-02-28 15:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 15:28 David Thompson [this message]
2015-02-28 17:17 ` [PATCHES] Propagate inputs for libxml2 and libxslt Andreas Enge
2015-02-28 19:37 ` 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=87zj7y6onw.fsf@fsf.org \
--to=dthompson2@worcester.edu \
--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).