Date: Thu, 13 Oct 2016 17:01:19 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 213446] Configurable verbose build output Message-ID: <bug-213446-13-kisiif1B2w@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 #7 from lightside <lightside@gmx.com> --- I contacted with core@ (and some other port's developers, including jbeich@, which email probably doesn't work, as stated in his comments currently) abo= ut this PR, where I included related links. I shared some concerns: - Increased I/O usage in console - Hard to find a warning messages, especially for CMake based projects, like LLVM/Clang, where verbose build output disables colored output, one line bu= ild messages, with duplicate for warning messages. This also may be related to = the size of the console buffer, where compact build output is more lightweight = on this. - There are people who use regular make, ports-mgmt/portmaster, ports-mgmt/synth, etc. and not just ports-mgmt/poudriere, where verbose out= put was enabled, because of BATCH=3Dyes define. If there are concerns about NO_VERBOSE_BUILD usage inside Makefile(s), ther= e is a possibility to move description of it to "special behavior" place: https://svnweb.freebsd.org/ports/head/Mk/bsd.port.mk?revision=3D421635&view= =3Dmarkup#l981 Also, I didn't ask to apply related patches for other ports, but may use NO_VERBOSE_BUILD check for my (private) ports. I'm not going to "play" close/open PR "games". --=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-kisiif1B2w>