On Sat, 15 Aug 2015 08:12:42 +0200 Paweł Hajdan, Jr. wrote:
> On 8/15/15 3:16 AM, Ian Stakenvicius wrote:
> > Secondly, though, conversion to EAPI5 is not actually trivial, there
> > are a couple of things, 'usex' related for instance, that also need
> > to be taken care of.  If it was just a matter of running a sed -e
> > 's/^EAPI=4/EAPI=5/' on all in-tree ebuilds this would have been done
> > a long time ago.
> 
> Do you mean that it would break things or just while technically working
> the ebuilds mass converted in this way would not take advantage of EAPI5
> features such use 'usex'?

Another issue: EAPI change normally requires revision bump.
Revision bump for stable packages will require stabilization
request in most cases (e.g. if all current stable versions are
<EAPI 5). Stabilization request often take ages.

Best regards,
Andrew Savchenko

Attachment: pgpxsQtXPg0eB.pgp
Description: PGP signature

Reply via email to