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