В Вск, 07/09/2008 в 15:34 +0100, Ciaran McCreesh пишет: > On Sun, 07 Sep 2008 17:24:55 +0400 > Peter Volkov <[EMAIL PROTECTED]> wrote: > > In any case as FHS and /usr/kde/<version> installations should set > > differently SLOT seems that new portage feature is required... May be > > portage should allow setting SLOT in dependence on USE flag? > > So what's the slot when SLOT="foo? ( 1 ) bar? ( 2 )"?
This syntax is not applying in our situation. Expression in SLOT should return only one value at a time. Something like this SLOT="foo:enabled?disabled" SLOT="foo:fooenabled?bar:barenabled?bardisabled" > And should you be able to have the same KDE version with both > USE=multislot and USE=-multislot installed at the same time? There are different SLOTs for different USE flags combination and package manager should allow installation same package in different SLOTs. But may be it's useful give developer possibility to disable that ( SLOT="foo::enabled?disabled" ). Ah, and this is bug 174407. > > Or new property for PROPERTIES called multislot which will workaround > > the problem with "invariancy of the SLOT"? > > Uh, how would that work? For ebuilds with such property (may be better name dynamicslot or dynslot) PM should source package with use flags set to get SLOT. Of course it's possible to cache results, sourcing package with all different USE flags combinations during cache generation. -- Peter.
