Ryan Hill posted on Tue, 06 Oct 2009 20:38:18 -0600 as excerpted: > I'd like to propose a new USE flag, qa-test or a better name, to handle > these cases in a consistent way. This would give us a way to > differentiate between tests that everyone should run and tests that only > devs and arch-testers would be interested in, making enabling > FEATURES=test by default in a future EAPI a little more palatable. > Use of this flag would be up to the maintainer, of course.
I'm confused. I'm sure there's a good reason for the different proposal here, but I don't know what it is, and I'd like to know: Previously there was discussion of RESTRICT=test, to be set for just such "user probably doesn't want this on" type situations. The proposal then was to turn FEATURES=test on by default for a specific EAPI, and then as packages moved to it, they'd add RESTRICT=test where appropriate (with a comment documenting why, of course), and anything of that EAPI or later that didn't have RESTRICT=test would automatically get built for and have its tests run by default. Now I see this proposal for making it a USE flag, which may or may not be more appropriate, I don't know. I do know I'd love to see someone explain the differences. -- 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
