1 |
On Tue, Jan 25, 2011 at 12:20:30PM +0100, Tomáš Chvátal wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> Hi, |
6 |
> I would like to upgrade tree-wide policy for EAPI usage in main tree. |
7 |
> Currently we say that developers can use any named version they wish or |
8 |
> find sufficient. |
9 |
> I would on other hand like to have all ebuilds to use Latest EAPI |
10 |
> version possible (given the eclasses support it [hint hint maintainers |
11 |
> of eclasses should always try to support latest :P]) with expection for |
12 |
> base-system or more specialy depgraph for portage that needs to be |
13 |
> EAPI0. [[ And here we need to find out some upgrade proccess that would |
14 |
> work for everyone so we could somehow migrate them too :)]] |
15 |
> |
16 |
> With this usually new developers should be aware only of latest EAPI and |
17 |
> wont need to memorize what which EAPI support. Heck even I sometimes |
18 |
> forget what i can do with some version and whatnot. |
19 |
> |
20 |
> Winner for being PITA in this race is python.eclass that HAS completely |
21 |
> different behavior based on EAPI version used... |
22 |
|
23 |
I agree with the idea, however, just creating the policy won't be |
24 |
enough. |
25 |
|
26 |
We should make repoman print a warning if an older EAPI is used, maybe |
27 |
even refuse to commit (without -f), at least on version bumps, to get |
28 |
the devs' attention. base-system excluded for now, obviously. |
29 |
|
30 |
> Cheers |
31 |
> |
32 |
> Tomas |
33 |
> -----BEGIN PGP SIGNATURE----- |
34 |
> Version: GnuPG v2.0.17 (GNU/Linux) |
35 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
36 |
> |
37 |
> iEYEARECAAYFAk0+sf4ACgkQHB6c3gNBRYeR6wCeNKsc8LnLw3ltkc1KKllzMP3u |
38 |
> bXMAnRlbWZjGpQ7Zc2abdxtoJFKRVszS |
39 |
> =lkXl |
40 |
> -----END PGP SIGNATURE----- |
41 |
|
42 |
-- |
43 |
Alex Alexander | wired |
44 |
+ Gentoo Linux Developer |
45 |
++ www.linuxized.com |