1 |
On Tue, 14 Aug 2012 23:09:55 +0200 |
2 |
Michał Górny <mgorny@g.o> wrote: |
3 |
> > We can't change inherit behaviour in EAPI 5 anyway since it's a |
4 |
> > global scope function, so I was planning to ignore it and hope that |
5 |
> > by the time EAPI 6 comes along, people will have learned not to |
6 |
> > write huge eclasses that do more than one thing. |
7 |
> |
8 |
> And why? I believe we have quite a clean rule that *EAPI goes before |
9 |
> inherit*. |
10 |
|
11 |
That rule will only start applying from EAPI 6 onwards. |
12 |
|
13 |
-- |
14 |
Ciaran McCreesh |