On Friday 30 December 2005 01:35, Spider (DmD Lj) wrote: > On Tue, 2005-12-27 at 19:06 +0000, Ciaran McCreesh wrote: > > On Tue, 27 Dec 2005 19:53:14 +0100 Carsten Lohrke <[EMAIL PROTECTED]> > > > > wrote: > > | On Tuesday 27 December 2005 18:59, Ciaran McCreesh wrote: > > | > Nnnope. If you modify an eclass it forces a cache regen for packages > > | > using said eclass (except possibly if you're using an overlay, but > > | > that's a separate issue...). > > | > > | You're trying to solve something which is already solved, but this > > | has nothing to do with our problem. The question is not listen the > > | possible valid KDE versions or a change of the eclass, but the need > > | to know actual used KDE version. You'd need to call e.g. kde-config > > | to get it. And this breaks caching. > > > > So you RDEPEND upon the version of KDE against which you were built, > > and use the || ( ) flattening feature that's already been proposed. > > Thats actually viable. For -installed- ebuilds, we simply unpack all > RDEPEND logic, remove all use flags ( stored, but the use logic is > removed from the RDEPEND since its already resolved, doesn't need to be > there. The binary is static already ) > > Then check vs. the installed SLOT of all RDEPEND packages, and lock our > current deptree to the package of that SLOT...
I suggested this last Tuesday.. > I can smell sooo much breakage from this solution. Even though it could > work : ) I'm not sure to interpret this as "yet another snide remark" or not so I'll give you the benefit of the doubt and assume you're referring to sets of ebuilds that require several slots. Before implementing the above, the tree will be checked for any cases where the above idea will fail. -- Jason Stubbs -- gentoo-dev@gentoo.org mailing list
