| 1 |
Am Donnerstag, 30. August 2012, 12:59:07 schrieb hasufell: |
| 2 |
> Could you elaborate what the reasons FOR it are (not that I don't know |
| 3 |
> any, but you brought it up) since this will add work for every developer |
| 4 |
> to check a) how the behavior of the new EAPI impacts the current ebuild |
| 5 |
> and b) how the behvaior of inherited eclasses change depending on EAPI. |
| 6 |
|
| 7 |
a) Easier eclass maintenance. |
| 8 |
Restricting the kde4 eclasses to EAPI 3 and 4 made the code indeed simpler. |
| 9 |
We'll raise that to 4 only soon (after fixing the remaining ebuilds in the |
| 10 |
tree.) |
| 11 |
|
| 12 |
b) Easier overall tree maintenance. |
| 13 |
I've recently removed a useflag on poppler (xpdf-headers for those |
| 14 |
interested). Of course, this involved fixing all in-tree reverse dependencies |
| 15 |
first. Now I consider myself very lucky there, because all except two packages |
| 16 |
were EAPI 4 and I could use (+). One package was EAPI 3 and I unceremoniously |
| 17 |
bumped it to 4. One was EAPI 0. Having fun with || there. |
| 18 |
|
| 19 |
I dont consider this list complete, feel free to add. |
| 20 |
|
| 21 |
-- |
| 22 |
Andreas K. Huettel |
| 23 |
Gentoo Linux developer |
| 24 |
kde (team lead), sci, tex, arm, printing |
| 25 |
dilfridge@g.o |
| 26 |
http://www.akhuettel.de/ |
Archives