| 1 |
>>>>> On Sat, 15 Aug 2015, Paweł Hajdan, wrote: |
| 2 |
|
| 3 |
> Nothing seems to prevent doing the mass conversion first, |
| 4 |
> deprecating EAPI 4, and then having a second, slower pass to make |
| 5 |
> sure the ebuilds are using EAPI 5 as they should be. One way might |
| 6 |
> be to add a "TODO" comment during mass conversion, which then can be |
| 7 |
> grepped for (and removed after manual review). |
| 8 |
|
| 9 |
How about a line like "EAPI=4" which can be grepped for? :) |
| 10 |
Seriously, what would be the benefit of a conversion if you need a |
| 11 |
second pass to redo it properly? |
| 12 |
|
| 13 |
Also there are still some 5000 ebuilds (14 %) with EAPIs 0, 1, 2, and |
| 14 |
3 in the tree. IMHO it would be better to spend our effort in updating |
| 15 |
those first. |
| 16 |
|
| 17 |
Ulrich |
Archives