BTW compilation warnings .. [tkloczko@domek SPECS.fedora]$ grep -- --disable-gcc-warnings *mingw-libtasn1.spec:%mingw_configure --disable-static *--disable-gcc-warnings*parted.spec:%configure --enable-selinux --disable-static *--disable-gcc-warnings* [tkloczko@domek SPECS.fedora]$ grep -- --disable-compile-warnings *anjuta.spec: *--disable-compile-warnings* \gnome-bluetooth.spec:%configure --disable-desktop-update --disable-icon-update --disable-schemas-compile *--disable-compile-warnings*gnome-desktop.spec: use *--disable-compile-warnings* instead.gnome-nettool.spec:%configure *--disable-compile-warnings*gnome-shell.spec: %configure --disable-static *--disable-compile-warnings*)libgnomekbd.spec: *--disable-compile-warnings* \
So at least in few packages seems like people are trying to cure fewer by breaking thermometer. If it is not already Fedora policy enable visibility of all compile time warnings to maximum level it should be official policy. 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. Regression tests can count those warnings raising alarms that something is changing here in wrong direction. Will try to take care of those few but it is possible that it is few more possible ways to lower compile time warnings verbosity level. kloczek -- Tomasz Kłoczko | LinkedIn: *http://lnkd.in/FXPWxH <http://lnkd.in/FXPWxH>*
_______________________________________________ devel mailing list -- devel@lists.fedoraproject.org To unsubscribe send an email to devel-le...@lists.fedoraproject.org
