Christopher Sawtell wrote: > Indeed, but speaking as a user, one wants the application to build and work, > that is after all the whole point of installing a package.
If you have it on the tree it is supposed to work or at least have passed a round of tests on the developer system, so you don't want a round of test run before installing it. > >> not having it tested. > That all depends. If having it tested means that it _will_ work, I'd be > infavour of that. However I do appreciate that having every user's install > repeating tests which have been done thousands of times before is probably > un-neccessary. having no way to opt out src_test at user level means that depending on the system you: - spend quite a lot of time to merge certain applications - got the application fail to merge because the tests fails because it is broken or has requirements completely unrelated to the application or the usage you planned for it - force me do more unnecessary work restricting and unrestricting tests on the ebuild level. > > How about setting the _default_ for test flags to true for '~' builds and > false for supposedly stable builds? you can do that FEATURES="test", that is the current situation, that works as should =P lu -- Luca Barbato Gentoo/linux Gentoo/PPC http://dev.gentoo.org/~lu_zero -- [EMAIL PROTECTED] mailing list
