| 1 |
On Sun, 8 Jul 2012 22:10:02 +0200 |
| 2 |
Michał Górny <mgorny@g.o> wrote: |
| 3 |
|
| 4 |
> On Sun, 08 Jul 2012 19:49:25 +0200 |
| 5 |
> René Neumann <lists@××××××.eu> wrote: |
| 6 |
> |
| 7 |
> > Hi all, |
| 8 |
> > |
| 9 |
> > I'd like just to receive a short clarification about the 'status' of |
| 10 |
> > base.eclass: Is this eclass expected to be available everywhere, |
| 11 |
> > i.e. should each eclass make sure it imports and incorporates it. |
| 12 |
> > Or is it just an eclass like the others and ebuilds should make |
| 13 |
> > sure they inherit it if needed? |
| 14 |
> |
| 15 |
> No. It is unmaintained, has serious design flaws and it simply should |
| 16 |
> not be used anywhere. At least in EAPI != [01]. |
| 17 |
> |
| 18 |
|
| 19 |
what is the PATCHES=() replacement in new eapis? (mainly why i use |
| 20 |
base.eclass more and more these days) |
Archives