On 09/14/2018 03:58 PM, Richard Yao wrote: >> >> No one has answered the question: what do you do when a stable package >> breaks because of a new warning? >> >> ...> > Wouldn’t this be largely covered as part of GCC stabilization? We could > reserve the right to kill -Werror in a package where it blocks GCC > stabilization if the maintainer does not handle it in a timely manner. >>
They would be uncovered during GCC stabilization, but then you're right back in the original situation: how do you fix the stable package? The only answer that doesn't violate some other policy is to patch it in a new revision and wait for it to stabilize again. Other questions arise: Do we block stabilization of clang et al.? If we can simply remove -Werror because it's been a month, were the warnings ever really important to begin with? How many packages do we want to make the toolchain team stop and fix before they can do their jobs?
