From: ludo@gnu.org (Ludovic Courtès)
To: John Darrington <jmd@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: libxft: Propagate input.
Date: Sat, 25 Jan 2014 16:38:51 +0100 [thread overview]
Message-ID: <871tzwul4k.fsf@gnu.org> (raw)
In-Reply-To: <87bnz0w0kn.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Sat, 25 Jan 2014 16:19:52 +0100")
ludo@gnu.org (Ludovic Courtès) skribis:
> John Darrington <jmd@gnu.org> skribis:
>
>> + (propagated-inputs
>> + `(("libxrender" ,libxrender))) ;; libxft refers to symbols in libxrender,
>> + ;; so without it, applications cannot be built.
>
> The only reasons I can think of where we may want to propagate are when:
>
> • installed C headers (or .scm, or Perl files, etc.) refer to headers
> of another library;
>
> • a .pc file lists another .pc in its ‘Requires’ field.
As we discussed on IRC, the reason is that xft.pc refers to ‘xrender’,
so I just put that in the comment.
Ludo’.
prev parent reply other threads:[~2014-01-25 15:44 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-23 20:07 [PATCH 1/3] gnu: libxft: Propagate input John Darrington
2014-01-23 20:07 ` [PATCH 2/3] gnu: fltk: New module John Darrington
2014-01-24 16:07 ` Thompson, David
2014-01-25 7:00 ` [PATCH 2/2] " John Darrington
2014-01-25 8:27 ` (unknown), John Darrington
2014-01-25 8:27 ` [PATCH] gnu: fltk: New module John Darrington
2014-01-25 15:39 ` Ludovic Courtès
2014-01-23 20:07 ` [PATCH 3/3] gnu: Add octave and dependencies John Darrington
2014-01-25 15:30 ` Ludovic Courtès
2014-01-25 16:14 ` John Darrington
2014-01-25 16:42 ` Andreas Enge
2014-01-25 17:04 ` John Darrington
2014-01-25 20:41 ` Ludovic Courtès
2014-01-26 7:38 ` John Darrington
2014-01-26 9:09 ` (unknown), John Darrington
2014-01-26 9:09 ` [PATCH] gnu: Add gnuplot John Darrington
2014-01-26 20:17 ` Ludovic Courtès
2014-01-26 18:54 ` [PATCH 3/3] gnu: Add octave and dependencies Andreas Enge
2014-01-26 19:30 ` Ludovic Courtès
2014-01-27 8:30 ` John Darrington
2014-01-27 9:11 ` Ludovic Courtès
2014-01-29 8:20 ` John Darrington
2014-01-29 21:26 ` Ludovic Courtès
2014-01-27 9:04 ` Sree Harsha Totakura
2014-01-27 9:53 ` Installing a C tool chain Ludovic Courtès
2014-01-27 10:32 ` Sree Harsha Totakura
2014-02-04 6:31 ` Mark H Weaver
2014-04-05 20:44 ` Ludovic Courtès
2014-04-14 17:54 ` Andreas Enge
2014-04-14 19:16 ` Ludovic Courtès
2014-04-14 19:43 ` Andreas Enge
2014-04-14 21:32 ` Ludovic Courtès
2014-04-14 21:57 ` Sergio Durigan Junior
2014-01-24 13:11 ` [PATCH 1/3] gnu: libxft: Propagate input Ludovic Courtès
2014-01-25 7:01 ` [PATCH 1/2] " John Darrington
2014-01-25 15:19 ` Ludovic Courtès
2014-01-25 15:38 ` 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=871tzwul4k.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=jmd@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).