Am Donnerstag, 30. August 2012, 12:59:07 schrieb hasufell: > Could you elaborate what the reasons FOR it are (not that I don't know > any, but you brought it up) since this will add work for every developer > to check a) how the behavior of the new EAPI impacts the current ebuild > and b) how the behvaior of inherited eclasses change depending on EAPI.
a) Easier eclass maintenance. Restricting the kde4 eclasses to EAPI 3 and 4 made the code indeed simpler. We'll raise that to 4 only soon (after fixing the remaining ebuilds in the tree.) b) Easier overall tree maintenance. I've recently removed a useflag on poppler (xpdf-headers for those interested). Of course, this involved fixing all in-tree reverse dependencies first. Now I consider myself very lucky there, because all except two packages were EAPI 4 and I could use (+). One package was EAPI 3 and I unceremoniously bumped it to 4. One was EAPI 0. Having fun with || there. I dont consider this list complete, feel free to add. -- Andreas K. Huettel Gentoo Linux developer kde (team lead), sci, tex, arm, printing dilfri...@gentoo.org http://www.akhuettel.de/
signature.asc
Description: This is a digitally signed message part.
