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