-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Brian Harring wrote: >>> Breaking EAPI=0 via pushing slot deps in isn't much of an option in >>> my opinion; usual "needs to have been on release media for at least 6 >> We can push for an EAPI=1 == (EAPI=0 + slot deps)... > > Can, yep, although that was originally blocked by "EAPI=0 must be > defined", which folks seem to have backed off on.
Not sure if slot deps themselves could even replace version ranges hacks without also solving bug 4315 (native version ranges) in all cases. IMHO it should be possible at least to specify slot+usual version limit, to make it worth EAPI bump. > One issue with adding EAPI=1 having just slot deps is that it skips > out on some long term changes intended- default src_install for So what, longer term changes could wait for EAPI=2. Why not make experience with EAPI bumping with something smaller for a start, instead of trying to make one big bump that will bring all changes we can think of now, but will be implemented only in 2010... Now it may look like I contradict myself saying to bump ASAP but not without solving bug 4315 first. But I see slot deps without limits only half of a feature. - -- Vlastimil Babka (Caster) Gentoo/Java -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGFXsstbrAj05h3oQRAid6AJ4lJldHuRwA0rHdr+CwGlth6zgG5wCgixJO 7PWG4j0nMOqdyR57bMW+r3E= =Cnya -----END PGP SIGNATURE----- -- gentoo-dev@gentoo.org mailing list
