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 1L6pfq-0007xw-1G for garchives@archives.gentoo.org; Sun, 30 Nov 2008 17:01:34 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 83333E05EF; Sun, 30 Nov 2008 17:01:32 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 4890DE05EF for ; Sun, 30 Nov 2008 17:01:32 +0000 (UTC) Received: from [192.168.1.33] (unknown [77.246.104.171]) (using TLSv1 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id A1E2E64651 for ; Sun, 30 Nov 2008 17:01:29 +0000 (UTC) Subject: Re: [gentoo-dev] [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official From: Peter Volkov To: gentoo-dev@lists.gentoo.org In-Reply-To: <4932BE8F.6030000@gentoo.org> References: <4932BE8F.6030000@gentoo.org> Content-Type: text/plain; charset="UTF-8" Date: Sun, 30 Nov 2008 20:00:55 +0300 Message-Id: <1228064455.25651.158.camel@localhost> 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 X-Mailer: Evolution 2.24.1.1 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: c2dd7e05-016e-44e4-8e7b-6434a19d6435 X-Archives-Hash: 3e44d8b33fdd3304f5133d4fee9b1828 Seems that we already have everything you dreamed about:=20 http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3D3&chap=3D1#= doc_chap4 Take a look at PORTAGE_ELOG_SYSTEM. It even can send that messages by mail :) HTH, -- Peter. =D0=92 =D0=92=D1=81=D0=BA, 30/11/2008 =D0=B2 09:25 -0700, Joe Peterson =D0= =BF=D0=B8=D1=88=D0=B5=D1=82: > Bottom line here is that there is extremely valuable and critical info > in our emerge output. In a way, these messages are like Gentoo-specifi= c > 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 i= s > 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). >=20 > 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). >=20 > In either case, there would then be a place to go that is known and > consistent (and can be documented in the Gentoo doc). It could, in > essense, serve as a kind of "Gentoo package README" collection. I coul= d > also imagine later expanding on this by letting a given package also > include more thorough README info from a file if the maintainer so desi= res.