Gentoo Archives: gentoo-dev

From: Zac Medico <zmedico@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] RFC: future.eclass
Date: Thu, 06 Nov 2014 20:40:42
Message-Id: 545BDCC1.5060305@gentoo.org
In Reply to: [gentoo-dev] RFC: future.eclass by "Michał Górny"
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

Replies

Subject Author
Re: [gentoo-dev] RFC: future.eclass Zac Medico <zmedico@g.o>
Re: [gentoo-dev] RFC: future.eclass Jeroen Roovers <jer@g.o>