1 |
On Tue, 14 Aug 2012 21:45:56 +0100 |
2 |
Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
3 |
|
4 |
> On Tue, 14 Aug 2012 11:44:49 +0200 |
5 |
> Michał Górny <mgorny@g.o> wrote: |
6 |
> > As some of you may have noticed, lately introduced 'double include |
7 |
> > preventions' have caused changes in effective phase functions in a |
8 |
> > few ebuilds. Also, often it is undesirable that change in inherits |
9 |
> > of an eclass may cause an undesired change of exported functions. |
10 |
> |
11 |
> The problem here is that eclasses aren't clearly split between |
12 |
> "utility" and "does stuff", so people are inheriting "does stuff" |
13 |
> eclasses to get utilities. The fix is to stop having stupidly huge |
14 |
> complicated eclasses; changing inherit behaviour is just wallpapering |
15 |
> over the gaping hole. |
16 |
|
17 |
Soo, how do you propose to handle bug 422533 without changing inherit |
18 |
behavior? |
19 |
|
20 |
-- |
21 |
Best regards, |
22 |
Michał Górny |