| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Hi, |
| 5 |
I would like to upgrade tree-wide policy for EAPI usage in main tree. |
| 6 |
Currently we say that developers can use any named version they wish or |
| 7 |
find sufficient. |
| 8 |
I would on other hand like to have all ebuilds to use Latest EAPI |
| 9 |
version possible (given the eclasses support it [hint hint maintainers |
| 10 |
of eclasses should always try to support latest :P]) with expection for |
| 11 |
base-system or more specialy depgraph for portage that needs to be |
| 12 |
EAPI0. [[ And here we need to find out some upgrade proccess that would |
| 13 |
work for everyone so we could somehow migrate them too :)]] |
| 14 |
|
| 15 |
With this usually new developers should be aware only of latest EAPI and |
| 16 |
wont need to memorize what which EAPI support. Heck even I sometimes |
| 17 |
forget what i can do with some version and whatnot. |
| 18 |
|
| 19 |
Winner for being PITA in this race is python.eclass that HAS completely |
| 20 |
different behavior based on EAPI version used... |
| 21 |
|
| 22 |
Cheers |
| 23 |
|
| 24 |
Tomas |
| 25 |
-----BEGIN PGP SIGNATURE----- |
| 26 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 27 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 28 |
|
| 29 |
iEYEARECAAYFAk0+sf4ACgkQHB6c3gNBRYeR6wCeNKsc8LnLw3ltkc1KKllzMP3u |
| 30 |
bXMAnRlbWZjGpQ7Zc2abdxtoJFKRVszS |
| 31 |
=lkXl |
| 32 |
-----END PGP SIGNATURE----- |
Archives