| 1 |
On 8/15/15 3:16 AM, Ian Stakenvicius wrote: |
| 2 |
> Secondly, though, conversion to EAPI5 is not actually trivial, there |
| 3 |
> are a couple of things, 'usex' related for instance, that also need |
| 4 |
> to be taken care of. If it was just a matter of running a sed -e |
| 5 |
> 's/^EAPI=4/EAPI=5/' on all in-tree ebuilds this would have been done |
| 6 |
> a long time ago. |
| 7 |
|
| 8 |
Do you mean that it would break things or just while technically working |
| 9 |
the ebuilds mass converted in this way would not take advantage of EAPI5 |
| 10 |
features such use 'usex'? |
| 11 |
|
| 12 |
mgorny@ mentioned the latter in another post, and I think we can address |
| 13 |
that e.g. by adding TODO comments to each ebuild converted this way for |
| 14 |
a manual review later. |
| 15 |
|
| 16 |
If you think this can actually break things, could you explain more? |
| 17 |
|
| 18 |
> Finally, the gentoo developer quiz -should- still contain questions |
| 19 |
> about ancient stuff. There are still EAPI0 and EAPI2 ebuilds in the |
| 20 |
> tree at least. |
| 21 |
|
| 22 |
EAPI0 can be tricky, but why don't we deprecate EAPI2? |
| 23 |
|
| 24 |
Paweł |
Archives