On 12/31/10 12:02, Ulrich Mueller wrote: > Hi, > > after approval of EAPI 4, there are now 5 different EAPIs available, > and it's hard to remember what features are offered by which EAPI. > > So maybe it's about time that we deprecate EAPIs 0 and 1 for new > ebuilds. As a first step, a warning could be added to repoman that > would be triggered whenever a new ebuild with an EAPI less than 2 is > committed.
That's a good idea. As long as there's a clean upgrade path from eapi0 left I'm all for it (and that is fragile - for example bash-completion has no eapi0 versions left, so currently it's really ugly to upgrade portage on an old install) > > At a later time, the warning could be changed to an error. When most > of the tree has been updated to EAPI 2 or newer, we could also think > about actively converting the remaining ebuilds. (Currently this > doesn't look feasible though, as about half of the tree is still at > EAPI=0. [1]) Since there's currently no need many ebuilds have never been upgraded. If people started actively working on it we could get that done in a short timeframe - but then I wonder if it's worth the effort.
