On 11/06/2014 12:40 PM, Zac Medico 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.
Now I realize that future.eclass has no way of knowing when mutilib or
eutils are inherited later. So, I can't think of a better way to handle
the collisions that what you already have.
--
Thanks,
Zac
