On Sun, 21 February 2010 Fabian Groffen <grob...@gentoo.org> wrote: > I recently proposed to enable this by default for cmake, but got some > negative feedback for that. Hence, I'd like to know the opinion of > more people on the issue. > > In the past we have had verbose build systems, that printed a lot of > messages. Portage even analyses this output to look for common > problems. Newer buildsystems (like cmake), or just newer insights > (like gnustep makefiles, linux kernel, git, ...) suppress more > messages leading to reduced output. > > - should we leave defaults of build systems as is, keeping some very > verbose and others very terse? > - should we always enable verbosity such that we can analyse logs, > both by Portage as well as in bugs when something apparently went > wrong? > - should make the output level consistent for all build systems? > > I think verbosity is useful when debugging problems. Portage's --jobs > feature nicely allows to hide the "ugly" output (even with --jobs=1), > still storing the log for when something goes wrong, while eliminating > the need to look at it all the time. > > So what do you think? Pros, cons?
IMHO the ideal solution would be to allow build-systems to be terse for successful operations but print the full command of the failing ones. That is, they would have to buffer output and show it only if the command failed. (they probably already have to buffer if parallel build should output consistent information) But this has probably to be solved on a larger scale than just Gentoo. Bruno
