From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([69.77.167.62] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1L6pZv-0007MB-Ik for garchives@archives.gentoo.org; Sun, 30 Nov 2008 16:55:27 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 46A69E0690; Sun, 30 Nov 2008 16:55:19 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 1E2E7E0690 for ; Sun, 30 Nov 2008 16:55:19 +0000 (UTC) Received: from [67.40.138.82] (crater.wildlava.net [67.40.138.82]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 598F064642 for ; Sun, 30 Nov 2008 16:55:18 +0000 (UTC) Message-ID: <4932C573.7040903@gentoo.org> Date: Sun, 30 Nov 2008 09:55:15 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.18 (X11/20081127) 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 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official References: <4932BE8F.6030000@gentoo.org> <20081130174609.0d543e02.genone@gentoo.org> In-Reply-To: <20081130174609.0d543e02.genone@gentoo.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: b458a510-3c48-409b-95ce-a711ff6bd82f X-Archives-Hash: dcdc8bd59de76d828003826c1140e51a Marius Mauch wrote: > By default, messages generated by elog, ewarn and eerror are recorded > in /var/log/portage/elog/summary.log (emerge.log is just a > transaction log, so best to ignore it here). einfo isn't recorded on > purpose as it isn't intended for important information (that's the > purpose of elog). There are some tools available to simplify reading > these messages, and there several additional/alternative delivery > modules available (by mail, IM or in package specific files), > customizable via POTAGE_ELOG_* variables. Don't know if you just > haven't been aware of this, or if you're asking for something > completely different. I'm really proposing something different - in essence, the above is to obscure to really serve as a good official kind of readme source for users. There needs to be something simple and straightforward (and well-documented) as the official thing to look at if one is having trouble with a package. In the case I mentioned all it took was for that user to see the messages, but it did not occur to him that the info would be there. I could even imagine that einfo should be included in what I am suggesting, since it may not be important for logging, but might be nice to have, nonetheless. -Joe