From: Ricardo Wurmus <rekado@elephly.net>
To: Guix-devel <guix-devel@gnu.org>
Subject: [PATCH]: gnu: lilv: propagate inputs serd, sord and sratom.
Date: Fri, 20 Feb 2015 22:04:30 +0100 [thread overview]
Message-ID: <87lhjsjnvl.fsf@mango.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 242 bytes --]
lilv-0.pc requires the packages serd, sord and sratom to be present or
else pkg-config fails when looking for the flags for lilv.
The attached patch moves serd, sord and sratom from lilv's inputs to the
propagated-inputs field.
~~ Ricardo
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-gnu-lilv-propagate-inputs-serd-sord-and-sratom.patch --]
[-- Type: text/x-patch, Size: 1131 bytes --]
From a253ab3b2ed89148211275938b5e574a594d8526 Mon Sep 17 00:00:00 2001
From: Ricardo Wurmus <rekado@elephly.net>
Date: Fri, 20 Feb 2015 21:56:51 +0100
Subject: [PATCH] gnu: lilv: propagate inputs serd, sord and sratom.
* gnu/packages/audio.scm (lilv): move serd, sord and sratom to propagated
inputs.
---
gnu/packages/audio.scm | 8 +++++---
1 file changed, 5 insertions(+), 3 deletions(-)
diff --git a/gnu/packages/audio.scm b/gnu/packages/audio.scm
index 40969ce..abd6f32 100644
--- a/gnu/packages/audio.scm
+++ b/gnu/packages/audio.scm
@@ -415,11 +415,13 @@ implementation of the Open Sound Control (OSC) protocol.")
"0aj2plkx56iar8vzjbq2l7hi7sp0ml99m0h44rgwai2x4vqkk2j2"))))
(build-system waf-build-system)
(arguments `(#:tests? #f)) ; no check target
- (inputs
- `(("lv2" ,lv2)
- ("serd" ,serd)
+ ;; required by lilv-0.pc
+ (propagated-inputs
+ `(("serd" ,serd)
("sord" ,sord)
("sratom" ,sratom)))
+ (inputs
+ `(("lv2" ,lv2)))
(native-inputs
`(("pkg-config" ,pkg-config)))
(home-page "http://drobilla.net/software/lilv/")
--
2.1.0
next reply other threads:[~2015-02-20 21:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 21:04 Ricardo Wurmus [this message]
2015-02-20 21:08 ` [PATCH]: gnu: lilv: propagate inputs serd, sord and sratom Andreas Enge
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lhjsjnvl.fsf@mango.localdomain \
--to=rekado@elephly.net \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.