Gentoo Archives: gentoo-dev

From: Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>
To: "Michał Górny" <mgorny@g.o>
Cc: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] How to handle dependencies on protocol headers?
Date: Fri, 16 Sep 2011 08:14:40
In Reply to: Re: [gentoo-dev] How to handle dependencies on protocol headers? by "Michał Górny"
On Fri, 16 Sep 2011 09:54:47 +0200
Michał Górny <mgorny@g.o> wrote:
> > 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. > > Please do not wreak exheres into Gentoo. The current variable forms > are complex enough; there is no reason to put even more logic into > the parser. And yes, it's better to have 7 *DEPEND variables than one > more magical, conditional thingie in the 'Dependencies' section.
From feedback so far, I think you're in the minority on that (at least from people who have expressed an opinion), and that more people have come out in favour of a single unified variable (not necessarily with exactly the same syntax as exheres-0). *shrug* I don't really mind about the syntax either way, and I suspect that'll come down to a Council decision. I do care about getting the exact definitions of what the various kinds of dependencies mean right -- as you saw in the "what's available in pkg_setup?" discussion, we have to be very very careful to avoid contradictions. I think we need at least the following classes to represent all the different dependencies people seem to need: Build dependencies (DEPEND): available in src_*. Run dependencies (RDEPEND): available when the package is used to satisfy a dependency. Install dependencies (IDEPEND?): available in pkg_setup. (Anyone interested in why this is necessary should see the "Rephrasing *DEPEND" thread on gentoo-pms. Sticking something in both DEPEND and RDEPEND isn't enough, since RDEPEND-RDEPEND cycles are breakable. But please read the original discussion before claiming we're wrong.) Build-against dependencies (BDEPEND?): the thing described in the original post in this thread. Post dependencies (PDEPEND): available sometime. Suggested dependencies (SDEPEND?): optionally available sometime. We may also want: Recommended dependencies (TDEPEND?): optionally available sometime, and chosen unless the user says not to. If we're trying to solve the SCM fetch problem in EAPI 5 (I don't think we are): Special Fetch dependencies (FDEPEND?): available during the special fetch phase, however we decide to do that. Note that suggested dependencies *have* to be PDEPEND-like. You can't sensibly have suggested DEPENDs, since that violates the "repeatable builds" principle. If something's an optional DEPEND, it needs a flag. -- Ciaran McCreesh


File name MIME type
signature.asc application/pgp-signature


Subject Author
Re: [gentoo-dev] How to handle dependencies on protocol headers? Brian Harring <ferringb@×××××.com>