Re: [gentoo-dev] RFC: future.eclass

[Jeroen Roovers]

On Thu, 06 Nov 2014 12:40:33 -0800
Zac Medico <zmedico@g.o> wrote:

> On 11/06/2014 12:11 PM, Michał Górny wrote:
> > # multilib.eclass collisions
> > get_libdir() { future_get_libdir "${@}"; }
> > # eutils.eclass collisions
> > einstalldocs() { future_einstalldocs "${@}"; }
>
> This collision handling mechanism seems pretty reasonable.
> Alternatively, maybe it could die if the functions are already
> defined, and advise the developer that future should be inherited
> later than multilib and eutils.

I'm not aware of any current definition of order in eclass inheritance.
We sure have issues with inheriting eclasses in a different order giving
different results now. Is this something that's in the works for a
future EAPI, then?


     jer