| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Dne 25.1.2011 14:33, Thomas Sachau napsal(a): |
| 5 |
> Do you have some more arguments for your request? Most new developers will have to know about all |
| 6 |
> EAPi versions anyway since they join an existing team with existing ebuilds, which will mostly not |
| 7 |
> use the newest EAPI. |
| 8 |
> |
| 9 |
> As an argument againt this: Noone forces you to keep older EAPI versions of the ebuilds you |
| 10 |
> maintain, you can always bump them to the latest EAPI. But why do you want to force this on all |
| 11 |
> developers? If i have an EAPI-0 ebuild and am fine with it, why should i convert it to the latest EAPI? |
| 12 |
> |
| 13 |
1) less stuff to memorize: |
| 14 |
seriously mostly if you just use latest EAPI and 0 you can make yourself |
| 15 |
not to bother for example with quirks required to use prefix properly in |
| 16 |
EAPI2 |
| 17 |
2) easier migration and deprecation of old EAPIs: |
| 18 |
If we enforce latest EAPI to be used EAPIs will be phased out by |
| 19 |
automatic upgrade process where we can migrate them. |
| 20 |
3) using less codepaths: |
| 21 |
so we can find out what the heck is wrong easier in both eclasses and |
| 22 |
portage if we know that it was hit with the latest code |
| 23 |
4) eapis are done to bring shiny features: |
| 24 |
usually ebuilds using new EAPI should be cleaner and easier to read than |
| 25 |
the old EAPI ones, by worst case scenario you just add the EAPI=Version |
| 26 |
line to the ebuild which makes it bit larger. |
| 27 |
|
| 28 |
>> |
| 29 |
>> Winner for being PITA in this race is python.eclass that HAS completely |
| 30 |
>> different behavior based on EAPI version used... |
| 31 |
> |
| 32 |
> The python eclass issues are not just EAPI related, the complete eclass is very complex and hard to |
| 33 |
> read/understand. And just because the eclass has additional EAPI-specific behaviour, this is |
| 34 |
> specific to this eclass and should not be an argument for the general EAPI discussion. |
| 35 |
> |
| 36 |
|
| 37 |
I just said that the eclass has different behaviour for each eapi. Which |
| 38 |
is true, nothing more nothing less. And you have to memorize it and |
| 39 |
check the behavior in reported bug with various EAPIs. |
| 40 |
|
| 41 |
Tomas |
| 42 |
-----BEGIN PGP SIGNATURE----- |
| 43 |
Version: GnuPG v2.0.17 (GNU/Linux) |
| 44 |
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ |
| 45 |
|
| 46 |
iEYEARECAAYFAk0+2YIACgkQHB6c3gNBRYdW/gCbB/Ki35r13CfUJPiaDNhgoAEO |
| 47 |
BfUAn3b/t9BEpU6Cd26btvCReTsizv66 |
| 48 |
=qFH3 |
| 49 |
-----END PGP SIGNATURE----- |
Archives