| 1 |
On Mon, 02 Aug 2010 23:55:07 +0200 |
| 2 |
Matti Bickel <mabi@g.o> wrote: |
| 3 |
> > No, you can't make global scope changes just in an EAPI without |
| 4 |
> > screwing up user systems. You have to do the whole "wait several |
| 5 |
> > years" thing for them. |
| 6 |
> |
| 7 |
> Bad. So I guess it's back to ferring's "use a new directory not |
| 8 |
> readable by old PMs" idea. GLEP55++, but having to wait several |
| 9 |
> months for that and GLEP33 *on top* is not very motivation for me. |
| 10 |
|
| 11 |
Unlike the other ways of allowing new global scope functions, GLEP 55 |
| 12 |
doesn't require a wait, and it doesn't require mass fixing of existing |
| 13 |
packages. That's part of the point of it. GLEP 55 can be rolled out and |
| 14 |
used as quickly as the code to support it in Portage is unreverted. |
| 15 |
|
| 16 |
-- |
| 17 |
Ciaran McCreesh |
Archives