Am 25.01.2011 15:09, schrieb Tomáš Chvátal:
> 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
> EAPI2

You are free to only use latest EAPI and EAPI-0 in your ebuilds. So you dont have to memorize the
changes in the other EAPI versions. But why do you want to force this on me too? I have to maintain
my ebuilds and have to debug the bugs for it, so why not give me the choice to use whatever i prefer
to use?

> 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.

Why would any migration be easier? You always have to check the difference between current and
planned EAPI during a migration, this wont change with the policy. And why do you want to deprecate
older EAPI versions?

> 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

As i said for the previous points: If you maintain something, you can use whatever you like,
including the latest versions, so this is no issue i can see.

> 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.

Sure, but if it is just another line and nothing else changes, why should i then even add that line?
I prefer to keep things to the minimum required and if it works fine for me without the additional
line, why should i add it?

> 
>>>
>>> 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.

This means, that you either have to convince the python eclass maintainers to reduce the complexity
of their eclass or you dont maintain ebuilds, which have to use their eclasses.

Alternatively you can just remember the behaviour for the latest EAPI and use that in your ebuilds,
so how does the different behaviour for previous EAPI versions create issues for you?

> 
> Tomas

-- 
Thomas Sachau

Gentoo Linux Developer