Michael Palimaka posted on Fri, 18 Nov 2016 02:35:26 +1100 as excerpted: > On 18/11/16 01:58, William Hubbs wrote: >> On Thu, Nov 17, 2016 at 06:16:27PM +1100, Michael Palimaka wrote: >>> ==== USE flags ==== >>> >>> While it is preferable to test every USE flag combination, this is not >>> always possible or appropriate. The package may have a large number of >>> USE flags, a long compile time, or the stabilisation in question may >>> just not call for it. >>> >>> In cases where all USE flags combinations are not being tested, it is >>> still recommended to test: >>> * with all USE flags enabled * with all USE flags disabled >> >> Does this mean we are changing our policy to support users running >> USE="-*"? I'm asking for clarification because in the past we have >> always told users that if they do that they are on their own. > > Testing with all USE flags disabled is more about catching build > failures than guaranteeing the package will necessarily do something > useful.
Along the same line but with all flags enabled, how does that apply to exclusive-or flags such as the qt4/qt5 thing that has been quite common? Sure common sense suggests "all" doesn't really mean "all" in that case, but given the opportunity presented by the update, if a guideline for the case can be made explicit... -- 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
