On 08/02/2010 10:15 PM, Ciaran McCreesh wrote:
> Aren't you really after per-package eclasses, not elibs?

Yes. I don't care whether the snippets may affect metadata. They already
don't (at one time they did, but we got warned that that's illegal -
that's why php-5.3 ebuilds have their metadata folded back into them).

>> Instead of all the backwards-compatibility issues the GLEP deals with,
>> we could just sneak the implementation into EAPI4 and be done with it.
> 
> No, you can't make global scope changes just in an EAPI without
> screwing up user systems. You have to do the whole "wait several years"
> thing for them.

Bad. So I guess it's back to ferring's "use a new directory not readable
by old PMs" idea. GLEP55++, but having to wait several months for that
and GLEP33 *on top* is not very motivation for me.