From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 3D90D13800E for ; Mon, 6 Aug 2012 11:08:27 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D1CEFE071E; Mon, 6 Aug 2012 11:08:08 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id D2FD021C004 for ; Mon, 6 Aug 2012 11:07:34 +0000 (UTC) Received: from pomiocik.lan (77-254-77-13.adsl.inetia.pl [77.254.77.13]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 53B621B4022; Mon, 6 Aug 2012 11:07:33 +0000 (UTC) Date: Mon, 6 Aug 2012 13:08:10 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Cc: chithanh@gentoo.org Subject: Re: [gentoo-dev] force verbose build log as per PMS policy? Message-ID: <20120806130810.1774477e@pomiocik.lan> In-Reply-To: <501F9B4C.6020401@gentoo.org> References: <50190F67.9060900@gentoo.org> <501F9B4C.6020401@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.11; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/dul1y+eCm=po4D.U=dbBxXa"; protocol="application/pgp-signature" X-Archives-Salt: a003f125-ab1d-481c-a753-4394fc9abfbb X-Archives-Hash: f24dbf97f1b9896d234b315585f7d390 --Sig_/dul1y+eCm=po4D.U=dbBxXa Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Mon, 06 Aug 2012 12:24:12 +0200 Ch=C3=AD-Thanh Christopher Nguy=E1=BB=85n 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=3D"--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 >=20 > Sorry that I am late to the party, but I would add some concerns to > this discussion. >=20 > 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. --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/dul1y+eCm=po4D.U=dbBxXa Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlAfpZoACgkQfXuS5UK5QB106AQAriE08b3HeFo7vQvwzaDLmW5v Sdr7KnSgL7PvAusCzdIhzu34SKaFvQ3lzjU3flfsLJnPFHl9FegQXjSByzi/Auku IA2FCuIWUIGM7xYYwfqNPM5D1iB2vSY9yvHZwqay12mHPxVHnAI+Z3pHmJ21m7bH fOcSu5Xd9FmzbjsMM+I= =JE7c -----END PGP SIGNATURE----- --Sig_/dul1y+eCm=po4D.U=dbBxXa--