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 1L7HMj-0002OK-TL for garchives@archives.gentoo.org; Mon, 01 Dec 2008 22:35:42 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 61454E03FB; Mon, 1 Dec 2008 22:35:40 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 3A974E03FB for ; Mon, 1 Dec 2008 22:35:40 +0000 (UTC) Received: from [192.168.1.103] (wireless3rd.boulder.swri.edu [65.241.78.19]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.gentoo.org (Postfix) with ESMTP id 7BADE64672 for ; Mon, 1 Dec 2008 22:35:39 +0000 (UTC) Message-ID: <493466B4.708@gentoo.org> Date: Mon, 01 Dec 2008 15:35:32 -0700 From: Joe Peterson User-Agent: Thunderbird 2.0.0.18 (Windows/20081105) 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> <1228168358.23326.6.camel@keitaro> In-Reply-To: <1228168358.23326.6.camel@keitaro> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Archives-Salt: 2308c8aa-73f5-4e69-b340-42e6227b552d X-Archives-Hash: 3eb8e3378b263278d0356a8cfb957cb2 Gilles Dartiguelongue wrote: > As others have said, there are already proper systems, documentation and > linking through other docs. Not finding this is what I'd call lazyness > or lack of google foo. Don't misunderstand me, some stuff can get ouf of > the radar of everyone, it's ok, real people are still here to point you > in the right direction. I think that I probably did not express my idea as well as I could have, since most of the responses I have gotten have echoed your thoughts that Gentoo does, indeed, have the facilities to achieve flexibility in logging, etc. I totally agree. Gentoo's capabilities, although not perfect, of course, are superlative and are a complement to its superb online doc. I think that's a big reason why we're all here - we see this and appreciate this. In fact, even when I do not include the word "gentoo" in a Google search, I more often than not end up at a Gentoo doc page - this is impressive. However, what I see as perhaps a missing "piece" is more conceptual: the important connection between the valuable info in the emerge logs (and their somewhat transient default nature) and what a user looks for when he/she has a problem with a package. Yes, users will realize this as they use Gentoo (and will start paying more attention to logs as a result), so I don't think it's a huge problem, but what this particular user said to me made me think that there is, perhaps, an opportunity to improve the situation. There is no Gentoo-specific "readme" facility, which could be the obvious and de facto place to go when trouble is had. I can imagine that a fairly simple and low-effort way of starting such a resource would be to simple echo the log output into a package-specific file in a known place (or put it in the portage db). The logging facilities allow similar things if configured to do it, but it is not on by default. Once users know where to go to see the "instructions" or "notes" on getting a package up and running after installation, this would become a good place to have such info or to expand on how the facility works. Starting with just the plain emerge log output would be an easy way to get benefit of such a concept has merit. And by no means would such a thing be an attempt to replace the excellent on-line docs or wiki, either - I see both as having unique strengths. For example, for detailed info on packages, the wiki/web stuff is the better resource. For a quick check of whether a revdep-rebuild might have been necessary after installing a new package would typically be in the log/notes. The notes also have the key advantage that they would *always* contain what the log output was, whereas whether a wiki or web page exists on a particular package depends on whether someone spent the time to author one. My intention with the RFC was to see if the concept has any worth and to kick it around a bit. I do not really see this as a deficiency in Gentoo's technology (which I have a feeling is how many here have interpreted it), but simply something that, if done correctly, could be useful. -Joe