On Tuesday 25 January 2011 20:13:40 Thomas Sachau wrote: > > The (maybe inofficial) suggestion is already to use the latest EAPI in new > ebuilds. This is ok for > me, as long as it is a suggestion. The same goes for the migration of ebuilds > to the latest EAPI. > But i am against the idea to enforce this for either new or even existing > ebuilds. I prefer to do > other work than useless EAPI-migration without a real need/benefit for me or > the users. >
This is fine as long as you do pure standalone work. As soon as you use a single eclass, you basically require the eclass maintainers to provide support for each and every EAPI - and that's an important point here. AFAIK the kde team will soon require EAPI (>)= 3 for all ebuilds using kde4-* eclasses. Similar restrictions already exist in other cases _in order to ease maintainability_. Why not go all the way and clean the mess out? -- Andreas K. Huettel Gentoo Linux developer - kde, sci, arm, tex [email protected] http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
