public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: chithanh@gentoo.org
Subject: Re: [gentoo-dev] force verbose build log as per PMS policy?
Date: Mon, 6 Aug 2012 13:21:35 +0200	[thread overview]
Message-ID: <20120806132135.514b735a@pomiocik.lan> (raw)
In-Reply-To: <20120806130810.1774477e@pomiocik.lan>

[-- Attachment #1: Type: text/plain, Size: 1357 bytes --]

On Mon, 6 Aug 2012 13:08:10 +0200
Michał Górny <mgorny@gentoo.org> wrote:

> On Mon, 06 Aug 2012 12:24:12 +0200
> Chí-Thanh Christopher Nguyễn <chithanh@gentoo.org> wrote:
> 
> > hasufell schrieb:
> > > 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 respected
> > > - 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 discussion.
> > 
> > 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
> > following happens:
> 
> About that -- maybe we should finally consider increasing it?
> Nowadays, HTTP is able to handle transparent compression, so plain
> text logs are pretty fine there.

https://bugs.gentoo.org/show_bug.cgi?id=430160

-- 
Best regards,
Michał Górny

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 316 bytes --]

      reply	other threads:[~2012-08-06 11:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 11:13 [gentoo-dev] force verbose build log as per PMS policy? hasufell
2012-08-01 15:27 ` Rich Freeman
2012-08-01 16:07 ` Michał Górny
2012-08-03 23:18   ` hasufell
2012-08-03 23:35     ` Diego Elio Pettenò
2012-08-04 19:03     ` Doug Goldstein
2012-08-04 19:18       ` hasufell
2012-08-01 16:43 ` Francesco Riosa
     [not found] ` <f56376345d2d4219986fe436c23f7279@HUBCAS1.cs.stonybrook.edu>
2012-08-01 22:22   ` Richard Yao
2012-08-06 10:24 ` Chí-Thanh Christopher Nguyễn
2012-08-06 11:08   ` Michał Górny
2012-08-06 11:21     ` Michał Górny [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120806132135.514b735a@pomiocik.lan \
    --to=mgorny@gentoo.org \
    --cc=chithanh@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox