| 1 |
>>>>> On Tue, 06 Mar 2018, Michał Górny wrote: |
| 2 |
|
| 3 |
> W dniu wto, 06.03.2018 o godzinie 18∶41 +0100, użytkownik Ulrich Mueller |
| 4 |
> napisał: |
| 5 |
>> > > > > > On Tue, 6 Mar 2018, Michał Górny wrote: |
| 6 |
>> > + 6) |
| 7 |
>> > + # for eqawarn |
| 8 |
>> > + [[ -z ${_EUTILS_ECLASS} ]] && inherit eutils |
| 9 |
>> > ;; |
| 10 |
>> |
| 11 |
>> NACK. With this you defeat the whole purpose of splitting things |
| 12 |
>> off from eutils. In turn, eutils inherits a dozen of other eclasses |
| 13 |
>> in EAPI 6. (Same for ltprune.eclass in patch 5/6.) |
| 14 |
|
| 15 |
> Yeah, you have a point there. Time to split eqawarn into its own |
| 16 |
> eclass? ;-) |
| 17 |
|
| 18 |
One-line eclass? :) |
| 19 |
|
| 20 |
No, I suggest to omit the deprecation part. With more than half of |
| 21 |
the tree at EAPI 6 already, it would be pretty late for deprecation |
| 22 |
warnings to be added for that EAPI. So simply do a clear-cut change |
| 23 |
for EAPI 7. |
| 24 |
|
| 25 |
Ulrich |
Archives