Mike Frysinger <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Fri, 13 Apr 2007 23:01:40 -0400:
> they realize they have no way at all of disabling the mandatory test ... > RESTRICT is an ebuild variable, not a package manager variable > this is why implementing it via the profile FEATURES works ... users can > still easily opt out and in case of some catastrofuck and we havent > screwed ourselves into a corner by mixing policy with spec Why not keep the feature but simply default it to ON instead of OFF? That's what I had assumed all along, and in fact seems to have been what was proposed since in several places the argument was that devs would be testing it anyway, thus implying the option remains NOT to test it. As I've said a couple times now, however, adding FEATURES=bigtest would IMO be useful, then let the ebuild use that for extra resource intensive tests or the like. Default would be FEATURES="test -bigtest", thus advancing the default QA for everyone, while continuing to allow users to opt-in/out entirely if desired. As for non-maintainer archs, the maintainer would test it on his arch, and arch-teams would test it on theirs before keywording stable. Those (like myself) running ~arch on non-maintainer archs should be prepared to live with the consequences of that choice anyway, including the occasional test failure on their arch because the maintainer didn't test it there and the arch-team hasn't gotten to it yet. -- 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
