Re: silent build rules

On Fri, 3 Apr 2009, Ralf Wildenhues wrote:
>
> A)
>
> 1) The developer can choose to enable the silent-rules option in
> configure.ac (as argument to AM_INIT_AUTOMAKE) or Makefile.am (adding
> the option to the AUTOMAKE_OPTIONS variable).  Without this option,
> there will never be less verbose output.
>
> 2) The developer or the maintainer can achieve the same effect as in (1)
> by adding the command line argument --silent-rules when running
> automake.
>
> 3) If (1) or (2) were done, then the user can enable less verbose output
> with ./configure --enable-silent-rules (the default is verbose).
>
> 4) If (3) as well as either (1) or (2) were done, then, at 'make' run
> time, less verbose output can be disabled with
>  make V=1
>
> Is that a compromise everybody can live with?

This is an approach that I am happy with.  I would not want to deny 
anyone access to silent rules if they want it (and I will am likely 
use it for my own developer builds), but feel that traditional verbose 
should continue to be the default.  Without traditional verbose being 
the default then GNU packages suddenly start to build differently, and 
the user is much less likely to be able to diagnose a problem by 
themselves without consuming time from the package maintainer.

Bob
--
Bob Friesenhahn
[email protected], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/