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. Is there any reason not to inherit future after multilib and eutils? I guess the reason would be some dependency on the old implementations? -- Thanks, Zac
