From: Ciaran McCreesh <ciaran.mccreesh@googlemail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How to handle dependencies on protocol headers?
Date: Fri, 16 Sep 2011 07:25:29 +0100 [thread overview]
Message-ID: <20110916072529.0b44999f@googlemail.com> (raw)
In-Reply-To: <CAEdQ38EpZVFZktC3LnT06YbXqC5iErmw6RhifEyAV0D9ftusSw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 928 bytes --]
On Fri, 16 Sep 2011 00:32:49 -0400
Matt Turner <mattst88@gentoo.org> wrote:
> Often packages depending on X11 libraries will also have to specify
> the X11 libraries' proto packages in DEPEND. This is because the X11
> library itself #includes files provided by the proto package. It's not
> really that the X11 library depends on this at run-time, so the
> protocol packages aren't specified in the RDEPEND of the libraries.
This is a build-against dependency, and it's best expressed either by
its own BADEPEND, or (because it's apparently now possible, and because
otherwise we'd end up with six or seven *DEPEND variables) by switching
to something like DEPENDENCIES with a build-against label.
If the Portage guys aren't winding us up when they say that they could
handle something like DEPENDENCIES without major code changes these
days, then it could be on the cards for EAPI 5.
--
Ciaran McCreesh
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-09-16 6:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-16 4:32 [gentoo-dev] How to handle dependencies on protocol headers? Matt Turner
2011-09-16 4:36 ` Alec Warner
2011-09-16 4:47 ` Matt Turner
2011-09-16 4:42 ` [gentoo-dev] " Matt Turner
2011-09-16 4:49 ` Zac Medico
2011-09-16 5:00 ` Alexander Bersenev
2011-09-16 5:24 ` Matt Turner
2011-09-16 6:25 ` Ciaran McCreesh [this message]
2011-09-16 7:54 ` [gentoo-dev] " Michał Górny
2011-09-16 8:08 ` Ciaran McCreesh
2011-09-16 9:15 ` Brian Harring
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=20110916072529.0b44999f@googlemail.com \
--to=ciaran.mccreesh@googlemail.com \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox