From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26041 invoked by uid 1002); 19 Aug 2003 23:53:41 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 10875 invoked from network); 19 Aug 2003 23:53:41 -0000 Date: Tue, 19 Aug 2003 19:53:39 -0400 From: Owen Gunden To: gentoo-dev@gentoo.org Message-ID: <20030819235338.GB5978@force.stwing.upenn.edu> Mail-Followup-To: gentoo-dev@gentoo.org References: <20030819053722.GA28151@force.stwing.upenn.edu> <200308190850.43935.kaschu@t800.ping.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200308190850.43935.kaschu@t800.ping.de> User-Agent: Mutt/1.5.4i Subject: Re: [gentoo-dev] patch: emergemail feature in functions.sh X-Archives-Salt: 170d75e4-1575-4c7b-839c-6f0fd526bef0 X-Archives-Hash: 936e8f767fd3384f7db8612228a7c0ed On Tue, Aug 19, 2003 at 08:50:43AM +0200, Karsten Schulz wrote: > what about collection all einfo/ewarn/eerror output in an ENV variable > (or in a temporary file) and send them in one mail to root after each > stage of the emerge process (compile, install, ...)? I took Karsten's advice and produced a new patch which doesn't have the major limitation of my last one. I've used it with a couple emerges already and I'm totally hooked :). See [1] for discussion and the patch. Owen References: 1. http://bugs.gentoo.org/show_bug.cgi?id=11359 -- gentoo-dev@gentoo.org mailing list