| 1 |
Michael Mol schrieb: |
| 2 |
> On Thu, Aug 30, 2012 at 9:14 AM, Rich Freeman <rich0@g.o> wrote: |
| 3 |
>> On Thu, Aug 30, 2012 at 9:04 AM, Ian Stakenvicius <axs@g.o> wrote: |
| 4 |
>>> |
| 5 |
>>> The primary benefit to the policy that dev's should bump EAPI when |
| 6 |
>>> bumping ebuilds is so that older inferior EAPIs can be deprecated and |
| 7 |
>>> eventually removed from the tree. |
| 8 |
>> |
| 9 |
>> What is the benefit from removing the old EAPIs? |
| 10 |
> |
| 11 |
> I can answer this one...removing old EAPIs simplifies code for things |
| 12 |
> which need to be EAPI-aware. There are no bugs in code that doesn't |
| 13 |
> exist. |
| 14 |
> |
| 15 |
|
| 16 |
Like package managers? |
| 17 |
|
| 18 |
Sorry, but this is not true, since you can never assume, that older |
| 19 |
EAPIs dont exist any more (even a simple EAPI-0 ebuild, which never |
| 20 |
needed a bump, is enough), so older EAPI versions have to be supported |
| 21 |
forever. |
| 22 |
|
| 23 |
-- |
| 24 |
|
| 25 |
Thomas Sachau |
| 26 |
Gentoo Linux Developer |
Archives