chithanh at gentoo
Aug 6, 2012, 3:24 AM
Post #10 of 12
Re: force verbose build log as per PMS policy?
[In reply to]
> When I sum that up again...
> - we are on gentoo and need as much information as possible for
> backtracing, resolving bugs, checking whether CFLAGS and such have been
> - no need to tell the user to recompile with
> EXTRA_ECONF="--disable-silent-rules" or similar just to be able to help him
> - some QA checks might depend on verbose build log and are not yet
> implemented therefor
> - if people want nice build _output_ (not log), they can use --quiet-build
Sorry that I am late to the party, but I would add some concerns to this
Verbose build logs are can be several times as large as non-verbose
ones, which can run into our Bugzilla's attachment size limit. When a
user is unable to attach the build.log file, typically one of the
1. User compresses build.log with a common compressor like gzip, bzip2
or xz and manually sets the attachment MIME type correctly (best case).
2. User makes a compressed tarball, containing a single file
3. User cuts off the build.log somewhere in the middle, supplies the
4. User uploads build.log to a public file hoster or his own private web
server, the link expires / 404s after some time (IMO worst case).
In my opinion, build verbosity should not be dictated by policy, but
rather left to the discretion of the maintainer. After all, he is the
one who needs to deal with the bug reports.
Having verbose build logs by default (with the possibility for the
maintainer to override) would be ok with me though.
Chí-Thanh Christopher Nguyễn