On Friday 30 December 2005 21:17, Spider (DmD Lj) wrote:
> On Fri, 2005-12-30 at 10:35 +0900, Jason Stubbs wrote:
> > 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]>
> > >
> > > 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..
>
> No, what you suggested was that for the case of when you depend on a
> SLOT, then the tree is flattened. My point was for the generic case :
>
> DEPEND=">=kde-base/kdelibs-3.0" (as many ebuilds look today)
>
> is then expanded to the current matching SLOT of kdelibs, so even if
> there -wasn't- a SLOT requirement beforehand, there is one afterwards.
Okay, I misinterpreted. Anyway, it looks like neither of our ideas will work:
app-text/docbook-sgml/docbook-sgml-1.0.ebuild:
RDEPEND="app-text/sgml-common app-text/openjade
>=app-text/docbook-dsssl-stylesheets-1.64
>=app-text/docbook-sgml-utils-0.6.6
~app-text/docbook-sgml-dtd-3.0
~app-text/docbook-sgml-dtd-3.1
~app-text/docbook-sgml-dtd-4.0
~app-text/docbook-sgml-dtd-4.1"
docbook-sgml-dtd-3.0-r3.ebuild:SLOT="3.0"
docbook-sgml-dtd-3.1-r3.ebuild:SLOT="3.1"
docbook-sgml-dtd-4.0-r3.ebuild:SLOT="4.0"
docbook-sgml-dtd-4.1-r3.ebuild:SLOT="4.1"
--
Jason Stubbs
--
gentoo-dev@gentoo.org mailing list
