Re: [gentoo-dev] RFC: [Future EAPI] Exporting phase funcs from direct inherits only

[Zac Medico <zmedico@gentoo.org>]

On 08/14/2012 01:54 PM, Michał Górny wrote:
> On Tue, 14 Aug 2012 21:45:56 +0100
> Ciaran McCreesh <ciaran.mccreesh@googlemail.com> wrote:
> 
>> On Tue, 14 Aug 2012 11:44:49 +0200
>> Michał Górny <mgorny@gentoo.org> wrote:
>>> As some of you may have noticed, lately introduced 'double include
>>> preventions' have caused changes in effective phase functions in a
>>> few ebuilds. Also, often it is undesirable that change in inherits
>>> of an eclass may cause an undesired change of exported functions.
>>
>> The problem here is that eclasses aren't clearly split between
>> "utility" and "does stuff", so people are inheriting "does stuff"
>> eclasses to get utilities. The fix is to stop having stupidly huge
>> complicated eclasses; changing inherit behaviour is just wallpapering
>> over the gaping hole.

Ciaran's assessment sounds pretty accurate to me.

> Soo, how do you propose to handle bug 422533 without changing inherit
> behavior?

Close it as WONTFIX. The ifndef thing that we're doing now seems like a
reasonable approach.
-- 
Thanks,
Zac