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 1L6pRa-0006cx-Di for garchives@archives.gentoo.org; Sun, 30 Nov 2008 16:46:50 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 21450E0656; Sun, 30 Nov 2008 16:46:47 +0000 (UTC) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.171]) by pigeon.gentoo.org (Postfix) with ESMTP id D539CE0656 for ; Sun, 30 Nov 2008 16:46:46 +0000 (UTC) Received: from sheridan (dslb-088-070-221-122.pools.arcor-ip.net [88.70.221.122]) by mrelayeu.kundenserver.de (node=mrelayeu3) with ESMTP (Nemesis) id 0MKxQS-1L6pRW0PnJ-0003Ls; Sun, 30 Nov 2008 17:46:46 +0100 Date: Sun, 30 Nov 2008 17:46:09 +0100 From: Marius Mauch To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official Message-Id: <20081130174609.0d543e02.genone@gentoo.org> In-Reply-To: <4932BE8F.6030000@gentoo.org> References: <4932BE8F.6030000@gentoo.org> X-Mailer: Sylpheed 2.4.8 (GTK+ 2.10.14; i686-pc-mingw32) 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: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX19xuQ9Bxcd9jOOnfYmFUdPYuJfiPkX1N3qUgvB lSjgzUE+KuBMS4l40uWAuml+NiMwlVlnc6I7kTIEVDftTsiASl G3OGBVIsAzvhmhM0QNJ3Q== X-Archives-Salt: 2bfb3079-9143-45c6-b169-775de29c68a2 X-Archives-Hash: b55747eb96b4134176a24723ba4dedeb On Sun, 30 Nov 2008 09:25:51 -0700 Joe Peterson wrote: > Bottom line here is that there is extremely valuable and critical info > in our emerge output. In a way, these messages are like > Gentoo-specific READMEs (or release notes and/or install > instructions). However, it is not saved for a user to use as a > resource later (well, except that it is partially saved in the master > emerge.log, but that's not quite useful enough). There is no > "official" place to go to look for Gentoo > instructions; /usr/share/doc is one logical place, but it only > contains files actually installed, not the notes output by emerge > (and these are usually upstream-supplied, not Gentoo). > > I propose that, upon merging a package, we save the emerge messages in > either: 1) a package-specific file that resides somewhere "official" > or > 2) in the portage DB, so that the messages can be re-read via a > portage utility. In the latter case, either a new option to "equery" > or a new "q" command (e.g. "equery readme " or "qreadme " > could retrieve the text). 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. Marius