From: Donnie Berkholz <dberkholz@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Dependencies that're available at pkg_*inst
Date: Fri, 18 Apr 2008 22:27:21 -0700 [thread overview]
Message-ID: <20080419052720.GE29470@supernova> (raw)
In-Reply-To: <20080419055420.29ab56e1@snowcone>
On 05:54 Sat 19 Apr , Ciaran McCreesh wrote:
> On Fri, 18 Apr 2008 21:45:13 -0700
> Donnie Berkholz <dberkholz@gentoo.org> wrote:
> > I'd go with RDEPEND only. Any other interpretation results in
> > installing build-time-only packages along with a binpkg, which
> > doesn't seem to make sense.
>
> That's definitely not what we want. Only a package's DEPENDs have to be
> installed and usable when that package is built. Its RDEPENDs don't
> have to be installed until that package is treated as usable.
I previously failed to clarify the situation I preferred because either
1 or 2b qualify as requiring RDEPEND to be installed.
My interpretation is pkg_* counts as runtime (I can imagine a package
wanting to run itself at this point), so packages in RDEPEND should be
usable at that point. Really, it seems to be an additional type of
dependency that neither DEPEND or RDEPEND fully describe, and this
DEPEND+RDEPEND idea isn't quite capturing it either. I say this because
I wouldn't want everything in DEPEND installed with a binpkg so it can
run pkg_*, and I also can see how some people wouldn't consider a
package in a runnable state until pkg_* have finished (so thus RDEPEND
shouldn't be required).
> For why this matters:
>
> cat/a-1: RDEPEND cat/b
> cat/b-1: RDEPEND cat/a
>
> This is solvable. If package managers can't solve this, they can't
> install Gnome off a stage 3...
Dealing with this under my interpretation is a bit weird. I think it
might need some sort of staging area. That's one reason I mentioned the
additional dep type.
Thanks,
Donnie
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-04-19 5:27 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-19 4:31 [gentoo-dev] Dependencies that're available at pkg_*inst Ciaran McCreesh
2008-04-19 4:45 ` Donnie Berkholz
2008-04-19 4:54 ` Ciaran McCreesh
2008-04-19 5:27 ` Donnie Berkholz [this message]
2008-04-19 5:33 ` Ciaran McCreesh
2008-04-19 7:43 ` Chris Gianelloni
2008-04-22 7:09 ` Ciaran McCreesh
2008-04-22 18:31 ` Chris Gianelloni
2008-04-19 18:53 ` [gentoo-dev] " Duncan
2008-04-19 23:55 ` Ciaran McCreesh
2008-04-21 5:17 ` [gentoo-dev] " Donnie Berkholz
2008-04-21 5:23 ` Ciaran McCreesh
2008-04-21 8:52 ` Marijn Schouten (hkBst)
2008-04-21 9:00 ` Ciaran McCreesh
2008-04-21 10:22 ` [gentoo-dev] " Duncan
2008-04-21 10:10 ` [gentoo-dev] " Luca Barbato
2008-04-21 10:15 ` Ciaran McCreesh
2008-04-21 10:05 ` Luca Barbato
2008-04-21 10:17 ` Arfrever Frehtes Taifersar Arahesis
2008-04-22 20:32 ` Doug Goldstein
2008-04-19 16:38 ` Marijn Schouten (hkBst)
2008-04-19 23:57 ` Ciaran McCreesh
2008-04-20 1:29 ` Brian Harring
2008-04-20 8:36 ` Ciaran McCreesh
2008-04-20 10:48 ` Santiago M. Mola
2008-04-22 20:31 ` Doug Goldstein
2008-04-27 9:41 ` [gentoo-dev] " Steve Long
2008-04-27 10:55 ` Ciaran McCreesh
2008-04-28 4:57 ` [gentoo-dev] " Steve Long
2008-04-28 12:13 ` Ciaran McCreesh
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=20080419052720.GE29470@supernova \
--to=dberkholz@gentoo.org \
--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