Markus Ullmann kirjoitti:
>> What if I want to use EAPI=1 features in an eclass? So if we for example
>> we have an ebuild using EAPI=2 and then it inherits and eclass that sets
>> EAPI=1 for slot deps.
> 
> shouldn't be an issue as eapi 1 and 2 would have slot deps
> though for other things like src functions defined in the eclass this
> might become really interesting, especially if we get src_configure in eapi2
> 
> Greetz
> Jokey
> 

You didn't get my point. Unless inherit has some EAPI handling logic
setting EAPI in an eclass would overwrite the one in the ebuild.

Regards,
Petteri