| 1 |
On Sat, Apr 28, 2012 at 12:26:41PM +0200, Ulrich Mueller wrote: |
| 2 |
> >>>>> On Sat, 28 Apr 2012, Ciaran McCreesh wrote: |
| 3 |
> |
| 4 |
> > On Sat, 28 Apr 2012 12:11:38 +0200 |
| 5 |
> > Ulrich Mueller <ulm@g.o> wrote: |
| 6 |
> >> >>>>> On Sat, 28 Apr 2012, Ciaran McCreesh wrote: |
| 7 |
> >> >> > * Get a versionator replacement into the PM |
| 8 |
> >> >> |
| 9 |
> >> >> Given the long time it's been in limbo I doubt that this will be a |
| 10 |
> >> >> quick feature. (But I'll be glad if you convince me of the |
| 11 |
> >> >> opposite.) |
| 12 |
> >> |
| 13 |
> >> > I thought we just didn't have that because we couldn't add new |
| 14 |
> >> > global scope functions. |
| 15 |
> >> |
| 16 |
> >> But can we already for EAPI 5? Wouldn't the following: |
| 17 |
> >> |
| 18 |
> >> EAPI=5 |
| 19 |
> >> MY_PV=$(new_pm_version_mangler_function ${PV}) |
| 20 |
> >> |
| 21 |
> >> still fail for old package managers that don't implement EAPI parsing? |
| 22 |
> |
| 23 |
> > Didn't the Council effectively vote to ignore that problem? |
| 24 |
> |
| 25 |
> Yes, but after some reasonable transition period. |
| 26 |
|
| 27 |
<insert my ongoing "Gee, lovely fucking approach to designing a |
| 28 |
compatibility mechanism"/> |
| 29 |
|
| 30 |
For EAPI5, all global scope functionality/bash version/take your pick |
| 31 |
has to be taken off the table, and held back till EAPI6- w/ the |
| 32 |
timeline for EAPI6 being "a reasonable transition period" after EAPI5 |
| 33 |
has been stabled in portage. |
| 34 |
|
| 35 |
~brian |
Archives