| 1 |
Ciaran McCreesh <ciaranm@×××××××.org> posted |
| 2 |
20070413203309.7df28d50@snowflake, excerpted below, on Fri, 13 Apr 2007 |
| 3 |
20:33:09 +0100: |
| 4 |
|
| 5 |
> On Fri, 13 Apr 2007 15:06:44 -0400 |
| 6 |
> Mike Frysinger <vapier@g.o> wrote: |
| 7 |
>> > If a test suite isn't viable, the ebuild should be RESTRICTing test |
| 8 |
>> > anyway. |
| 9 |
>> |
| 10 |
>> which doesnt apply here ... some packages have ridiculous awesome |
| 11 |
>> coverage for their source code and take much longer to run than even |
| 12 |
>> compile the package |
| 13 |
>> |
| 14 |
>> care to force mysql test suites on everyone ? php ? gcc ? binutils ? |
| 15 |
> |
| 16 |
> A separate solution is needed for those anyway, since there're plenty of |
| 17 |
> people running with FEATURES=test. |
| 18 |
|
| 19 |
FEATURES=bigtest ?? |
| 20 |
|
| 21 |
Interesting idea. Then default test to on and bigtest to off, with |
| 22 |
appropriate user descriptions and developer guidelines for when use of |
| 23 |
"bigtest" is appropriate (extra deps, long runtime, etc.). |
| 24 |
|
| 25 |
-- |
| 26 |
Duncan - List replies preferred. No HTML msgs. |
| 27 |
"Every nonfree program has a lord, a master -- |
| 28 |
and if you use the program, he is your master." Richard Stallman |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives