| 1 |
On 08/02/2010 10:15 PM, Ciaran McCreesh wrote: |
| 2 |
> Aren't you really after per-package eclasses, not elibs? |
| 3 |
|
| 4 |
Yes. I don't care whether the snippets may affect metadata. They already |
| 5 |
don't (at one time they did, but we got warned that that's illegal - |
| 6 |
that's why php-5.3 ebuilds have their metadata folded back into them). |
| 7 |
|
| 8 |
>> Instead of all the backwards-compatibility issues the GLEP deals with, |
| 9 |
>> we could just sneak the implementation into EAPI4 and be done with it. |
| 10 |
> |
| 11 |
> No, you can't make global scope changes just in an EAPI without |
| 12 |
> screwing up user systems. You have to do the whole "wait several years" |
| 13 |
> thing for them. |
| 14 |
|
| 15 |
Bad. So I guess it's back to ferring's "use a new directory not readable |
| 16 |
by old PMs" idea. GLEP55++, but having to wait several months for that |
| 17 |
and GLEP33 *on top* is not very motivation for me. |
Archives