On 02/10/2014 09:35 AM, Tom Wijsman wrote:
one and possibly needed features. You will connect the question of
>"are we ready to deprecate X" with the question "we need to introduce
>Y for needed features a, b and c."
It is hard to grasp for me for when features from a newer EAPI would
delay the migration, do you have an example?
That's not what i mean. It is possible that we may want the newer EAPI
for the features it brings but be as yet unwilling to deprecated the
older EAPI for stability reasons. Even if the newer EAPI is a proper
superset of the older, hidden implementation changes have not been
tested well and we might want to be more caution about deprecating our
older yet very stable EAPI. EAPI=4 is very stable right now. I have
more confidence in it that 5 simply because of the coverage and testing
its gotten.
--
Anthony G. Basile, Ph.D.
Gentoo Linux Developer [Hardened]
E-Mail : bluen...@gentoo.org
GnuPG FP : 1FED FAD9 D82C 52A5 3BAB DC79 9384 FA6E F52D 4BBA
GnuPG ID : F52D4BBA
