| 1 |
On Tue, 14 Aug 2012 14:09:17 -0700 |
| 2 |
Zac Medico <zmedico@g.o> wrote: |
| 3 |
|
| 4 |
> On 08/14/2012 01:54 PM, Michał Górny wrote: |
| 5 |
> > On Tue, 14 Aug 2012 21:45:56 +0100 |
| 6 |
> > Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> wrote: |
| 7 |
> > |
| 8 |
> >> On Tue, 14 Aug 2012 11:44:49 +0200 |
| 9 |
> >> Michał Górny <mgorny@g.o> wrote: |
| 10 |
> >>> As some of you may have noticed, lately introduced 'double include |
| 11 |
> >>> preventions' have caused changes in effective phase functions in a |
| 12 |
> >>> few ebuilds. Also, often it is undesirable that change in inherits |
| 13 |
> >>> of an eclass may cause an undesired change of exported functions. |
| 14 |
> >> |
| 15 |
> >> The problem here is that eclasses aren't clearly split between |
| 16 |
> >> "utility" and "does stuff", so people are inheriting "does stuff" |
| 17 |
> >> eclasses to get utilities. The fix is to stop having stupidly huge |
| 18 |
> >> complicated eclasses; changing inherit behaviour is just |
| 19 |
> >> wallpapering over the gaping hole. |
| 20 |
> |
| 21 |
> Ciaran's assessment sounds pretty accurate to me. |
| 22 |
> |
| 23 |
> > Soo, how do you propose to handle bug 422533 without changing |
| 24 |
> > inherit behavior? |
| 25 |
> |
| 26 |
> Close it as WONTFIX. The ifndef thing that we're doing now seems like |
| 27 |
> a reasonable approach. |
| 28 |
|
| 29 |
But you're aware that this 'reasonable approach' just made the whole |
| 30 |
problem by changing exported functions, right? |
| 31 |
|
| 32 |
-- |
| 33 |
Best regards, |
| 34 |
Michał Górny |
Archives