From: Andreas Enge <andreas@enge.fr>
To: guix-devel@gnu.org
Subject: Re: [PATCH 1/5] gnu: Add efl.
Date: Sun, 1 Mar 2015 21:21:58 +0100 [thread overview]
Message-ID: <20150301202158.GA9832@debian> (raw)
In-Reply-To: <20150301194309.GA26151@venom>
On Sun, Mar 01, 2015 at 08:43:09PM +0100, tcech@suse.cz wrote:
> On Sun, Mar 01, 2015 at 08:24:54PM +0100, Andreas Enge wrote:
> >You could also try to move them to normal inputs and see whether another
> >package depending on efl still compiles.
> I'm afraid that I found what propagated-input is thanks to this. I'm
> sure that elementary or others won't build without that.
Sorry, what I suggested as a test actually does not work. The question is:
Does everything built with efl requires the additional libraries, or may
there be packages building with efl, but without these additional libraries?
Of course, no finite number of examples constitutes a proof...
I found the following:
http://people.freedesktop.org/~dbn/pkg-config-guide.html
Requires: A list of packages required by this package. The versions of these packages may be specified using the comparison operators =, <, >, <= or >=.
Requires.private: A list of private packages required by this package but not exposed to applications. The version specific rules from the Requires field also apply here.
This sounds as if only "Requires" libraries need to be propagated, whereas
"Requires.private" libraries are already handled by our ld wrapper.
The page above links to the following:
https://wiki.openmandriva.org/en/Overlinking_issues_in_packaging
This seems to confirm my opinion, but it would be good if someone more
knowledgeable on pkg-config could comment on the issue.
Andreas
next prev parent reply other threads:[~2015-03-01 20:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-28 22:11 EFL, elementary, loaders, players and terminology - round 2 Tomáš Čech
2015-02-28 22:11 ` [PATCH 1/5] gnu: Add efl Tomáš Čech
2015-03-01 19:24 ` Andreas Enge
2015-03-01 19:43 ` tcech
2015-03-01 20:21 ` Andreas Enge [this message]
2015-03-01 20:26 ` Ludovic Courtès
2015-03-01 20:31 ` Ludovic Courtès
2015-02-28 22:11 ` [PATCH 2/5] gnu: Add elementary Tomáš Čech
2015-03-01 20:33 ` Ludovic Courtès
2015-02-28 22:11 ` [PATCH 3/5] gnu: Add evas-generic-loaders Tomáš Čech
2015-03-01 20:34 ` Ludovic Courtès
2015-02-28 22:11 ` [PATCH 4/5] gnu: Add emotion-generic-players Tomáš Čech
2015-03-01 20:35 ` Ludovic Courtès
2015-02-28 22:11 ` [PATCH 5/5] gnu: Add terminology Tomáš Čech
2015-03-01 20:36 ` Ludovic Courtès
-- strict thread matches above, loose matches on Subject: below --
2015-02-26 0:31 [PATCH 1/5] gnu: Add efl Tomáš Čech
2015-02-26 20:58 ` Andreas Enge
2015-02-26 21:05 ` Andreas Enge
2015-02-27 16:56 ` 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=20150301202158.GA9832@debian \
--to=andreas@enge.fr \
--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).