On jeu., 2011-09-01 at 05:21 +0100, Ben Hutchings wrote: > As I wrote on #605090: > > Without the strict check, the crap code produces a compile-time warning > and a run-time warning and *no copying*. With the strict check, the > crap code results in FTBFS (but only on i386 and s390!). So how is this > an improvement for us? That mean we can catch issues earlier, at least on those arches (and if they trigger on theses arches that surely means they exist on the others). The warning is good, but are those really seen in the huge build log? Maybe all the relevant crap code is detected before it reaches debian buildd and thus we don't need the FTBFS, but I'm still unsure. Or maybe just enable it for trunk/-rc packages and not in sid/ builds (I can understand that FTBFS are a pain but in those cases I'm not sure warnings are sufficient). Regards, -- Yves-Alexis
Attachment:
signature.asc
Description: This is a digitally signed message part