Hi, On Sat, 15 Aug 2015 00:05:57 +0200 Johannes Huber wrote: > if we want to attract more contributors we should consider to have one > supported EAPI (latest). EAPI 4 is the last not marked as deprecated > (< EAPI 5). The move in ebuilds from EAPI 4 to EAPI 5 is very simple > replacing the declaration. As we have now git in place we could easily > do this with one commit (awesome!!!!). > > So please discuss this to get it ready for decision on next council > meeting.
Are all eclasses ready for this transition? I remember time when there were issues with python still demanding EAPI 4, while EAPI 5 in tree. This is no longer issue these days, but we hay have similar issues with other eclasses. What about compatibility with overlays? What if EAPI 4 ban will hurt them (e.g. if relevant code will be dropped from eclasses). While I have no objections about EAPI 4 deprecation (except concerns mentioned above), I see no strong need for this also. Just declare EAPI 5 as recommended. Having legacy support for EAPI 4 will not hurt possible contributions. Best regards, Andrew Savchenko
pgph90LrJq9yy.pgp
Description: PGP signature
