From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.60) (envelope-from <gentoo-user+bounces-54871-garchives=archives.gentoo.org@gentoo.org>) id 1GkmRX-0001vk-QU for garchives@archives.gentoo.org; Thu, 16 Nov 2006 18:58:36 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kAGIrxjx018564; Thu, 16 Nov 2006 18:53:59 GMT Received: from flyingjoke.org (soggy88.drizzle.com [216.162.199.88]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kAGIncum016775 for <gentoo-user@lists.gentoo.org>; Thu, 16 Nov 2006 18:49:40 GMT Received: (qmail 24510 invoked from network); 16 Nov 2006 18:49:36 -0000 Received: from atlantis.flyingjoke.org (192.168.1.8) by atlantis.flyingjoke.org with SMTP; 16 Nov 2006 18:49:36 -0000 Date: Thu, 16 Nov 2006 10:49:29 -0800 (PST) From: David Talkington <dtalk@prairienet.org> X-X-Sender: dtalk@atlantis.flyingjoke.org To: gentoo-user@lists.gentoo.org Subject: [gentoo-user] Re: pet peeve: sending normal output to stderr (env-update) In-Reply-To: <7573e9640611141245w456ee863yde01fdf8c268156@mail.gmail.com> Message-ID: <Pine.LNX.4.64.0611161040500.23548@atlantis.flyingjoke.org> References: <Pine.LNX.4.64.0611140948000.23548@atlantis.flyingjoke.org> <7573e9640611141245w456ee863yde01fdf8c268156@mail.gmail.com> Precedence: bulk List-Post: <mailto:gentoo-user@lists.gentoo.org> List-Help: <mailto:gentoo-user+help@gentoo.org> List-Unsubscribe: <mailto:gentoo-user+unsubscribe@gentoo.org> List-Subscribe: <mailto:gentoo-user+subscribe@gentoo.org> List-Id: Gentoo Linux mail <gentoo-user.gentoo.org> X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Archives-Salt: 24499ee3-7ae8-4491-bafc-b4c158a6171c X-Archives-Hash: d256bf13142ac617f4d61653470f8487 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Richard Fish wrote: > env-update.sh outputs this message with a simple "echo", so no output > to stdout here. However portage writes most ">>>" messages to stderr. Well and good, but this is not an abnormal message, and there's no reason for it to go to stderr. stderr is for errors, else it's just unbuffered stdout, which isn't terribly helpful. File descriptor gymnastics and text munging should not be required in order to separate expected output from abnormal conditions. I expect that from Microsoft. ;-) > You can either file a bug report on bugs.gentoo.org to try and get the > behavior changed, Thank you, I'll look into that. Obviously, I was merely venting here. Cheers -d - -- David Talkington PGP key: http://www.prairienet.org/~dtalk/004B8F8B.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFXLLA5FKhdwBLj4sRAr9eAJkBO7D7empiwxkA7+MriXL4tkx5sQCfaZXV 8rPuON/F03fbU5SCuxFrucQ= =3WNZ -----END PGP SIGNATURE----- -- gentoo-user@gentoo.org mailing list