On Tue, 30 Jan 2007 13:01:47 -0500 Alec Warner <[EMAIL PROTECTED]> wrote:
> Marius Mauch wrote: > > 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. > > > > 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: > > > > The idea is to add a special category (let's call it "active" for now) that > > has the following properties: > > - this category doesn't exist in portdir or vdb (= no ebuilds) > > - 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 > > > > (and yes, this kinda goes with multi-repo/multi-format support) > > > > Marius > > I don't see why how this is any less complicated than just adding more > functionality to || deps (runtime versus compile time) 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? Marius -- [email protected] mailing list
