| 1 |
Carsten Lohrke wrote: |
| 2 |
> On Freitag, 20. Februar 2009, Petteri Räty wrote: |
| 3 |
>> Suggestions/objections? |
| 4 |
> |
| 5 |
> If you mean by "mass migration" doing that more or less blindly, I do object. |
| 6 |
> When an ebuild directly or indirectly inherits an eclass, which is EAPI 2 |
| 7 |
> enabled, like base.eclass, while another isn't, you have to expect |
| 8 |
> side-effects. See for example media-tv/kdetv-0.8.9-r1, which features an |
| 9 |
> empty src_prepare to prevent the attempt to apply patches twice, temporarily. |
| 10 |
> |
| 11 |
> So the first step is to get all eclasses EAPI 2 ready and even then I wouldn't |
| 12 |
> rule out odd cases, so changes should happen in testing and revised ebuilds |
| 13 |
> exclusively to assure odd cases get caught. |
| 14 |
> |
| 15 |
> |
| 16 |
> Carsten |
| 17 |
|
| 18 |
Yes of course not without testing the packages. The point here was also |
| 19 |
that if you are maintaining something do the change yourself before the |
| 20 |
next bug day. Even if the eclasses are not EAPI 2 ready you can work |
| 21 |
around it in the ebuild by for example those empty functions. |
| 22 |
|
| 23 |
Regards, |
| 24 |
Petteri |
Archives