1 |
On 11/06/2014 12:11 PM, Micha³ Górny wrote: |
2 |
> # multilib.eclass collisions |
3 |
> get_libdir() { future_get_libdir "${@}"; } |
4 |
> # eutils.eclass collisions |
5 |
> einstalldocs() { future_einstalldocs "${@}"; } |
6 |
|
7 |
This collision handling mechanism seems pretty reasonable. |
8 |
Alternatively, maybe it could die if the functions are already defined, |
9 |
and advise the developer that future should be inherited later than |
10 |
multilib and eutils. Is there any reason not to inherit future after |
11 |
multilib and eutils? I guess the reason would be some dependency on the |
12 |
old implementations? |
13 |
-- |
14 |
Thanks, |
15 |
Zac |