On Sun, Mar 19, 2017 at 02:46:35AM +0000, Tomasz Kłoczko wrote: > If it is not already Fedora policy enable visibility of all compile time > warnings to maximum level it should be official policy. No. There's a policy to show the full command line option, but that's not the same. Most warnings are only useful for upstream developers, and packagers are not (and should not) do anything about them. One obvious case is unused variables and functions, especially in generated code. Another is stylistic variations for old but valid code. Yet another could be the new fall-through warnings in switch statements. Etc, etc. There's also the case of potentially useful warnings, which are wrong (e.g. about unitialized variables with -O2 or -O3), and it's impossible to get rid of those warnings except by altering the code in an unwanted way. So this strongly depends on the individual package, and setting options to silence unuseful warnings is totally reasonable (e.g. by making logs more readable). > Why? because URLs to build logs from koji could be used to present exact > compile time warnings asking source code maintainers to fix those issues. If you need that, you can always recompile. This happens too rarely to matter. Zbyszek _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
