| 1 |
> > <rant> |
| 2 |
[...] |
| 3 |
> > standards. So, we declare that gcc-4.5 has to be enough for everyone, |
| 4 |
> > we'll just keep it in tree forever and dont bother anymore with all |
| 5 |
> > these superfluous "does not build with gcc-4.7" bugs. |
| 6 |
> |
| 7 |
> That is not an appropriate analogy, as I'm not suggesting that we |
| 8 |
> refuse to support newer EAPIs. I'm just saying that packages |
| 9 |
> shouldn't be bumped just for the sake of bumping them. |
| 10 |
|
| 11 |
Well I'm also not "suggesting" that we refuse to support newer gcc. Just, if a |
| 12 |
package does not build with newer, meh, why care. Take old one. |
| 13 |
</rant> |
| 14 |
|
| 15 |
> I might see some benefit for devs who routinely modify stuff that they |
| 16 |
> don't maintain, but that should generally be kept to a minimum anyway. |
| 17 |
> If unsure how how to edit any particular ebuild, just file a bug! |
| 18 |
> And if the package isn't maintained, then nobody will be bumping its |
| 19 |
> EAPI anyway. |
| 20 |
|
| 21 |
True but... we do have some fluctuation, and developers come and go. Who can |
| 22 |
update the ebuild better, someone who has maintained it for a while and is |
| 23 |
familiar with its details and the current eapis, or someone who has just |
| 24 |
picked up its pieces. |
| 25 |
|
| 26 |
What I dont actually understand at all is why bumping the EAPI should be so |
| 27 |
complicated or involved that it even deserves so much resistance... |
| 28 |
|
| 29 |
OK there may be miraculous eclasses (or one in particular) which change api |
| 30 |
radically from eapi to eapi, but I think we've already decided long time ago |
| 31 |
that this is a bad thing(tm) and should not be done. So let's hope it will not |
| 32 |
happen again. |
| 33 |
|
| 34 |
Other than that, I can not remember any ebuild where the EAPI bump alone took |
| 35 |
me more than 5min. Now take the frequency of new eapi's coming out, and |
| 36 |
compare it with the time that you need for a version bump of a package anyway |
| 37 |
(check upstream changelog, verify dependencies have not changed, do a test |
| 38 |
build, check for correct installation locations, ...) |
| 39 |
|
| 40 |
As an additional bonus this keeps your memory fresh about all the great new |
| 41 |
features... |
| 42 |
|
| 43 |
Cheers, |
| 44 |
Andreas |
| 45 |
|
| 46 |
-- |
| 47 |
|
| 48 |
Andreas K. Huettel |
| 49 |
Gentoo Linux developer |
| 50 |
dilfridge@g.o |
| 51 |
http://www.akhuettel.de/ |
Archives