> If, as a user or an arch person, I get a src_test failure right now, I > don't know whether this means "eek! Something's gone wrong, and I > really need to fix this" or "oh, whoever maintains this package > doesn't care". But with EAPI 2, I'll be able to know that a src_test > failure really does mean "something's wrong". >
A developer should always care about src_test in my opinion. That some developers don't is a nuisance, and the core of the problem. But trying to change this via EAPI is doing things the wrong way round: At first there has to be an agreement about the importance of test suites (backed up by strict policies that every developer is bound to), and then we can discuss if it makes sense to activate them by default in EAPI-X.
signature.asc
Description: This is a digitally signed message part
