Re: [gentoo-project] Re: Call for agenda items - Council meeting 2013-04-09

[Thomas Sachau]

Ulrich Mueller schrieb:
> One agenda item I'd like to add myself is EAPI deprecation (again).
> We're collecting items for EAPI 6 already, and with this being
> deployed there would be seven EAPIs in use.
>
> http://qa-reports.gentoo.org/output/eapi_usage.txt says:
>
>    repository '/usr/portage':
>      eapi: '4' 12928 pkgs found, 39.10% of the repository
>      eapi: '0' 7041 pkgs found, 21.29% of the repository
>      eapi: 'unsupported' 4630 pkgs found, 14.00% of the repository
>      eapi: '2' 4289 pkgs found, 12.97% of the repository
>      eapi: '3' 3748 pkgs found, 11.34% of the repository
>      eapi: '1' 429 pkgs found, 1.30% of the repository
>
>    Date generated: Tue Apr  2 13:03:17 UTC 2013
>
> We already "encourage" using the newest EAPI, see 20110308 meeting.
> (Though I fail to find this recommendation in the devmanual, shouldn't
> it be there?)
>
> Should we have a stricter rule? Would such a rule help significantly
> reducing the number of EAPI 0 ebuilds?
>
> Ulrich
>

If a newer EAPI contains a feature usefull for me, i will update the
EAPI of the ebuild to use this feature, but otherwise, why should i
change the EAPI (and have additional work), when there is no reason?

So what do we gain from a stricter rule forcing the usage of specific
EAPI versions?

-- 

Thomas Sachau
Gentoo Linux Developer