Ciaran McCreesh <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Fri, 13 Apr 2007 20:33:09 +0100:
> On Fri, 13 Apr 2007 15:06:44 -0400 > Mike Frysinger <[EMAIL PROTECTED]> wrote: >> > If a test suite isn't viable, the ebuild should be RESTRICTing test >> > anyway. >> >> which doesnt apply here ... some packages have ridiculous awesome >> coverage for their source code and take much longer to run than even >> compile the package >> >> care to force mysql test suites on everyone ? php ? gcc ? binutils ? > > A separate solution is needed for those anyway, since there're plenty of > people running with FEATURES=test. FEATURES=bigtest ?? Interesting idea. Then default test to on and bigtest to off, with appropriate user descriptions and developer guidelines for when use of "bigtest" is appropriate (extra deps, long runtime, etc.). -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- [EMAIL PROTECTED] mailing list
