| 1 |
On Sat, 15 Aug 2015 08:12:42 +0200 Paweł Hajdan, Jr. wrote: |
| 2 |
> On 8/15/15 3:16 AM, Ian Stakenvicius wrote: |
| 3 |
> > Secondly, though, conversion to EAPI5 is not actually trivial, there |
| 4 |
> > are a couple of things, 'usex' related for instance, that also need |
| 5 |
> > to be taken care of. If it was just a matter of running a sed -e |
| 6 |
> > 's/^EAPI=4/EAPI=5/' on all in-tree ebuilds this would have been done |
| 7 |
> > a long time ago. |
| 8 |
> |
| 9 |
> Do you mean that it would break things or just while technically working |
| 10 |
> the ebuilds mass converted in this way would not take advantage of EAPI5 |
| 11 |
> features such use 'usex'? |
| 12 |
|
| 13 |
Another issue: EAPI change normally requires revision bump. |
| 14 |
Revision bump for stable packages will require stabilization |
| 15 |
request in most cases (e.g. if all current stable versions are |
| 16 |
<EAPI 5). Stabilization request often take ages. |
| 17 |
|
| 18 |
Best regards, |
| 19 |
Andrew Savchenko |
Archives