List Archive: gentoo-dev
Note: Due to technical difficulties, the Archives are currently not up to date.
provides an alternative service for most mailing lists.c.f. bug 424647
-----BEGIN PGP SIGNED MESSAGE-----
Dne 25.1.2011 14:33, Thomas Sachau napsal(a):
> Do you have some more arguments for your request? Most new developers will have to know about all
> EAPi versions anyway since they join an existing team with existing ebuilds, which will mostly not
> use the newest EAPI.
> As an argument againt this: Noone forces you to keep older EAPI versions of the ebuilds you
> maintain, you can always bump them to the latest EAPI. But why do you want to force this on all
> developers? If i have an EAPI-0 ebuild and am fine with it, why should i convert it to the latest EAPI?
1) less stuff to memorize:
seriously mostly if you just use latest EAPI and 0 you can make yourself
not to bother for example with quirks required to use prefix properly in
2) easier migration and deprecation of old EAPIs:
If we enforce latest EAPI to be used EAPIs will be phased out by
automatic upgrade process where we can migrate them.
3) using less codepaths:
so we can find out what the heck is wrong easier in both eclasses and
portage if we know that it was hit with the latest code
4) eapis are done to bring shiny features:
usually ebuilds using new EAPI should be cleaner and easier to read than
the old EAPI ones, by worst case scenario you just add the EAPI=Version
line to the ebuild which makes it bit larger.
>> Winner for being PITA in this race is python.eclass that HAS completely
>> different behavior based on EAPI version used...
> The python eclass issues are not just EAPI related, the complete eclass is very complex and hard to
> read/understand. And just because the eclass has additional EAPI-specific behaviour, this is
> specific to this eclass and should not be an argument for the general EAPI discussion.
I just said that the eclass has different behaviour for each eapi. Which
is true, nothing more nothing less. And you have to memorize it and
check the behavior in reported bug with various EAPIs.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.17 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
-----END PGP SIGNATURE-----