[Bug 213446] Configurable verbose build output

[bugzilla-noreply at freebsd.org]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213446

--- Comment #24 from lightside <lightside at gmx.com> ---
(In reply to comment #0)
> with using NO_VERBOSE_BUILD define, e.g. NO_VERBOSE_BUILD=yes in
> /etc/make.conf or `make NO_VERBOSE_BUILD=yes` for concrete port to
> disable verbose build output or without it to enable.
There is also following possible use case (with mentioned changes from comment
#20) in /etc/make.conf:
-8<--
.ifndef VERBOSE
LESS_VERBOSE=yes
.endif
-->8-
which allows to use `make VERBOSE=yes` to get full verbose build output when
needed (and less verbose build output otherwise), as it was before ports
r421635 changes.

Needed to say, that previously this was more granular, with usage of
CMAKE_VERBOSE, NINJA_VERBOSE, etc. (and possible CONFIGURE_VERBOSE, WAF_VERBOSE
proposals). This was possible to configure for concrete build cluster (not just
BATCH=yes), without the need to force mandatory full verbose build output usage
for ports framework's users, in my opinion. Moreover, there was no need to use
"good" and "bad" biased opinions about different levels (or types) of the same
information for documentation:
https://www.freebsd.org/doc/en/books/porters-handbook/dads-verbose-logs.html
https://svnweb.freebsd.org/doc/head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml?view=markup&pathrev=49378#l325
But possible explanation about preferences when submitting (full verbose) build
logs to FreeBSD Bugzilla (or maintainer(s)).

As you may know, the (current) portmgr@ team (or some of them) chose more
simple, but restrictive methods.

-- 
You are receiving this mail because:
You are on the CC list for the bug.