On Monday, 27 February 2017 14:30 Michael Matz wrote:
Apart from the dubiosity of having to visually scan log files to find warnings and errors (see above), even if you then find them. What then? You don't have the compiler command line, so you don't know which flags were active and if you want to fix the problem you have to fiddle with the .spec anyway to activate verboseness (in whatever way it needs it). (Well, or of course you randomly do changes and rebuild until the warning/error goes away).
From my point of view, the problem is that with verbose log, I most likely won't notice a warning at all. With non-verbose build, each warning sticks out and is hard to miss. Actually, I don't really agree with the claim that I always need the command line. I rarely do, most of the time, the information from gcc (what problem, which file, line number, include chain) is sufficient to see what the warning is about. Full command line is useful when I want to repeat the particular command; but this is only possible for local builds and even then it's not always trivial; for builds running in OBS I can't do it anyway. Right now I'm looking at a verbose build log and found a warning in it. Relevant command line (which I don't need at all) is 7 lines higher (where "line" is actually more than 3 lines on a 271 columns wide terminal) and two more such lines are intermixed with the warning itself. With non-verbose log, the warning would be way easier to both spot and read. Well, whatever. Personally I hope this verbosity enforcing will only apply to OBS builds and there will be a way to work around it for local builds ("osc build"). If it only applies to "official" projects (and not home:*), I would be even happier. Michal Kubeček -- To unsubscribe, e-mail: opensuse-packaging+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-packaging+owner@opensuse.org