On Tue, 2007-08-07 at 12:20 +0100, Ciaran McCreesh wrote: > Which is why it's so important to catch failures. Something that builds > correctly for a developer may not build correctly for a user, so being > strict will help prevent users from installing a broken package.
Personally I agree with being strict and catching as many failures as possible. I would be in favor of catching do* related errors and have them fail only FEATURES="strict", or perhaps "stricter". That will still cause a clear failure for people running with "strict" (and which dev isn't...). If you don't want to be bothered by the QA stuff then simply don't set "strict". I do this on my work laptop, while I use "strict" on my dev machine to catch as many problems as possible so that I can fix them or report bugs on them. Kind regards, Hans
signature.asc
Description: This is a digitally signed message part
