Re: making QUIET_BUILD the default

[James Lowe]

On 29/12/15 08:52, Werner LEMBERG wrote:
> Is there a particular reason to no making `QUIET_BUILD' the default?
> For Metafont, it's extremely chatty otherwise...
>
> On the other hand, I suggest to change
>
>   ifdef QUIET_BUILD
>   LILYPOND_BOOK_WARN = --loglevel=NONE
>   else
>   LILYPOND_BOOK_WARN = --loglevel=WARN
>   endif
>
> to
>
>   ifdef QUIET_BUILD
>   LILYPOND_BOOK_WARN = --loglevel=ERROR
>   else
>   LILYPOND_BOOK_WARN = --loglevel=WARN
>   endif
>
> in file `make/lilypond-vars.make' to still have fatal errors sent to
> stderr.
>
>
>     Werner
>
> _______________________________________________
> lilypond-devel mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-devel
>
>
There was some discussion about this back in 2011/12 - when I first
started with the LP project.

http://lists.gnu.org/archive/html/lilypond-devel/2011-08/msg00378.html

I seem to recall that Phil was involved with the 'changing' of log
levels and it was he that did the check-ins.

(e.g.

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=c0b2076349f9b3715242cc38c1238e3e6d5489f2

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=38b47996485336eb01d9698f3f52e36f6bb9b0af

http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=2d93d73606b64e39c9b4cbb451a9c5f3887c60ec

etc


Essentially it's a balance. For those that don't make doc it probably
seems more of an issue, but for those that do when testing patches (i.e.
me) this made my life so much easier in trying to workout what the
issues were.

So if you want the logs then you should be able to enable whatever
verbosity you need. For the rest of us, the log levels are fine thanks.

;)

-- 
James

-------

B8F4 5395 CBE2 ED37 7513 B075 FF32 5682 A84B D8BE