Ciaran McCreesh wrote: > > Unfortunately, it looks like this proposal's one of those things that > some people will hate for ideological reasons no matter what. I just > hope there're enough people on the Council for whom QA and user systems > not breaking is sufficiently important that they'll vote in favour of > it. >
While I support enabling test by default I'm about to do a "foot in mouth" moment and suggest something that is far too over complicated This is a compromise between those that want tests by default and those who don't and has these simple rules 1) Tests are enabled by default for ~arch ebuilds. 2) Tests are _not_ enabled by default for stable ebuilds. ~arch users will therefore have to explicitly disable tests and run the risks associated with that. My guess is that arch users are also the ones more likely to have CFLAGS or LDFLAGS that are significantly different from the defaults hopefully enabling tests will catch all the issues we know that are going to have. arch users will have to explicitly enable tests, but hopefully by the time a package has been marked stable it has had its unit tests ( oh im pointing that foot in mouth again ) run enough times to verify its correctness.
