Gentoo Archives: gentoo-portage-dev

From: Marius Mauch <genone@g.o>
To: gentoo-portage-dev@l.g.o
Subject: Re: [gentoo-portage-dev] [RFC] Depending on "active" version
Date: Tue, 30 Jan 2007 19:58:49
Message-Id: 20070130210923.a58c7775.genone@gentoo.org
In Reply to: Re: [gentoo-portage-dev] [RFC] Depending on "active" version by Alec Warner
1 On Tue, 30 Jan 2007 13:01:47 -0500
2 Alec Warner <antarus@g.o> wrote:
3
4 > Marius Mauch wrote:
5 > > Sometimes a package has to depend on a specific version of a slotted package being the "active" one to build correctly, like in the current "tr1" discussion on -dev [1] or with packages that depend on the running kernel.
6 > >
7 > > Currently this isn't really possible, however I while ago I got an idea how to solve this. Keep in mind this is just a rough idea and I'm pretty sure some people can/will point out why it is a stupid idea, but anyway:
8 > >
9 > > The idea is to add a special category (let's call it "active" for now) that has the following properties:
10 > > - this category doesn't exist in portdir or vdb (= no ebuilds)
11 > > - when portage ($pkgmanager) encounters a "active/foo" atom in a dependency string it executes some special code (e.g. "$PORTDIR/scripts/active-check/foo =active/foo-1") to determine if that atom is satisfied
12 > >
13 > > (and yes, this kinda goes with multi-repo/multi-format support)
14 > >
15 > > Marius
16 >
17 > I don't see why how this is any less complicated than just adding more
18 > functionality to || deps (runtime versus compile time)
19
20 Please explain. If a package can only be built if the currently running kernel is higher than 2.6.19 for example, how would you possibly express that in *DEPEND syntax?
21
22 Marius
23 --
24 gentoo-portage-dev@g.o mailing list