On Tue, 09 Aug 2011 19:14:27 +0200, Adam Jackson wrote:
If you're volunteering to fix and/or paper over all the spurious warnings gcc and glibc introduce with every phase of the moon, then sure.
Yes, I do it for my component, GDB has -Werror default in development phases upstream. It cleans up the code, it finds various minor bugs etc.
Otherwise -Werror would essentially mean never shipping anything ever again.
So the maintainers either care about the warnings - and then they should use -Werror - or they do not care about the warnings - and then it does not matter regarding warning messages which and how many of them can be found on the Koji server in the log files. Please decide.
As always I guess it should be per maintainer / per package. Something like default -Werror with easy opt-out. And we can forget about hiding the compilation commands useful for toolchain troubleshooting.
Thanks, Jan