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 15D241381F3 for ; Tue, 3 Sep 2013 21:45:07 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 13ECEE14A6; Tue, 3 Sep 2013 21:44:55 +0000 (UTC) Received: from jacques.telenet-ops.be (jacques.telenet-ops.be [195.130.132.50]) by pigeon.gentoo.org (Postfix) with ESMTP id D2D7FE142F for ; Tue, 3 Sep 2013 21:44:53 +0000 (UTC) Received: from TOMWIJ-GENTOO ([94.226.55.127]) by jacques.telenet-ops.be with bizsmtp id Llkn1m0152khLEN0JlknjS; Tue, 03 Sep 2013 23:44:48 +0200 Date: Tue, 3 Sep 2013 23:44:45 +0200 From: Tom Wijsman To: gentoo-dev@lists.gentoo.org Cc: alan.mckinnon@gmail.com Subject: Re: [gentoo-dev] Re: Can we have process names and stdout / stderr indication to more efficiently parse build logs? Message-ID: <20130903234445.29f82b7e@TOMWIJ-GENTOO> In-Reply-To: <5226530D.1090607@gmail.com> References: <20130902192152.GB1762@linux1> <20130903022232.0d78832b@TOMWIJ-GENTOO> <21029.40175.488797.249157@a1i15.kph.uni-mainz.de> <20130903190314.GA5627@linux1> <20130903221128.6797c114@TOMWIJ-GENTOO> <5226496A.9090104@gmail.com> <5226530D.1090607@gmail.com> X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.20; 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-SHA1; boundary="Sig_/h+1vd1.FaCs98IzwDeBYbt="; protocol="application/pgp-signature" X-Archives-Salt: 26390283-0b90-410f-aee1-eb463201fb75 X-Archives-Hash: 87467038ed00fac7820bc32a7aca47ce --Sig_/h+1vd1.FaCs98IzwDeBYbt= Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Tue, 03 Sep 2013 23:22:21 +0200 Alan McKinnon wrote: > So do what we've always done in Unix-land: leave the decision up to > the user. Build logs can always be regenerated (run emerge again) if > the ANSI sequences truly are vital whilst troubleshooting a specific > log. And we already do this for localized logs if the dev can't make > sense of non-English messages. It only becomes a problem if the log > is for one of that small number of loooooong builds (libreoffice, > kdelibs etc) +1 I am still not convinced we are experiencing an actual practical problem for the majority of the build logs that are attached; we've been doing this for years, why is it so suddenly considered a problem? --=20 With kind regards, Tom Wijsman (TomWij) Gentoo Developer E-mail address : TomWij@gentoo.org GPG Public Key : 6D34E57D GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D --Sig_/h+1vd1.FaCs98IzwDeBYbt= Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.21 (GNU/Linux) iQEcBAEBAgAGBQJSJlhNAAoJEJWyH81tNOV9w2AH/32Ja2o5mKCZouTDz/qL2fjq s91PCOXb+LA0hKdgPAsTpnocOs1W2vjyopNWyuUj60N7jdWsRtJfmEai2QrZHH8n uzSGv6JoTcjgF8g5eecUArTL6K+Flib5e7KHEW+cx/lMP4N5jMdm8M9z9Ey1clxH JDNRtMnxcXngDjquwsrtVMPBwAhcFg8k1FupgxdSAwMUoHbCoflJna5AMo32h/5N Eoh1AVZzq2P1BBx+atyKA3LAWcxOmc5hqiJsIj6DnSXdlb0eyenE0evXAWEnay7N sf2dCPhvYOJhgINe8DQCOmLxEFmtkarjdqfPZmjBn4nGCaAca8TYk2sDDMQIbeU= =7cRO -----END PGP SIGNATURE----- --Sig_/h+1vd1.FaCs98IzwDeBYbt=--