On Monday March 09 Ciaran McCreesh wrote: > > * src_test run unless RESTRICTed or explicitly disabled by the user > (bug 184812)
Yes, and I would go even further: keep src_test for unit tests and some kind of pkg_posttest for either a routine to test the package once installed or an elog test recipe, a bit like the emacs testing plans. It could be useful for arch testers, guis, and revdep tests. It would force packagers to define an omitted src_test when upstream actually had one. As mentioned by Christian, src_test is desirable in sci packages to get consistent results, but sci packages depend on lots of others, so you can't limit tests to some categories. And yes, you can't revdep test everything, but you can reduce bug load. It seems to be controversial, so unfortunately does not look like a good candidate for a flash EAPI upgrade. But really, don't dismiss it just because your pet package doesn't pass tests or it takes too long. One solution for packages taking too long to compile is not dismissing tests but a good binary package system. -- Sébastien
signature.asc
Description: PGP signature
