| 1 |
El dom, 08-07-2012 a las 22:59 +0200, René Neumann escribió: |
| 2 |
> Am 08.07.2012 22:10, schrieb Michał Górny: |
| 3 |
> > On Sun, 08 Jul 2012 19:49:25 +0200 |
| 4 |
> > René Neumann <lists@××××××.eu> wrote: |
| 5 |
> > |
| 6 |
> >> Hi all, |
| 7 |
> >> |
| 8 |
> >> I'd like just to receive a short clarification about the 'status' of |
| 9 |
> >> base.eclass: Is this eclass expected to be available everywhere, i.e. |
| 10 |
> >> should each eclass make sure it imports and incorporates it. Or is it |
| 11 |
> >> just an eclass like the others and ebuilds should make sure they |
| 12 |
> >> inherit it if needed? |
| 13 |
> > |
| 14 |
> > No. It is unmaintained, has serious design flaws and it simply should |
| 15 |
> > not be used anywhere. At least in EAPI != [01]. |
| 16 |
> > |
| 17 |
> |
| 18 |
> Thanks for the clarification. As Mike already mentioned, one should |
| 19 |
> probably change the ebuild description to reflect just that fact. |
| 20 |
> (Because at the moment it just says the complete opposite.) |
| 21 |
> |
| 22 |
> - René |
| 23 |
> |
| 24 |
|
| 25 |
And, if we are supposed to stop using it, it should print some kind of |
| 26 |
warning to remember developers to drop its usage |
Archives