Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Oct 2016 02:34:21 +0000
From:      bugzilla-noreply@freebsd.org
To:        freebsd-ports-bugs@FreeBSD.org
Subject:   [Bug 213446] Configurable verbose build output
Message-ID:  <bug-213446-13-VhvCb2w1ml@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-213446-13@https.bugs.freebsd.org/bugzilla/>
References:  <bug-213446-13@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213446

--- Comment #24 from lightside <lightside@gmx.com> ---
(In reply to comment #0)
> with using NO_VERBOSE_BUILD define, e.g. NO_VERBOSE_BUILD=3Dyes in
> /etc/make.conf or `make NO_VERBOSE_BUILD=3Dyes` for concrete port to
> disable verbose build output or without it to enable.
There is also following possible use case (with mentioned changes from comm=
ent
#20) in /etc/make.conf:
-8<--
.ifndef VERBOSE
LESS_VERBOSE=3Dyes
.endif
-->8-
which allows to use `make VERBOSE=3Dyes` to get full verbose build output w=
hen
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_VER=
BOSE
proposals). This was possible to configure for concrete build cluster (not =
just
BATCH=3Dyes), 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 s=
ame
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=3Dmarkup&pathrev=3D49378#l325
But possible explanation about preferences when submitting (full verbose) b=
uild
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.

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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-213446-13-VhvCb2w1ml>