Gentoo Logo
Gentoo Spaceship

Installation:
Gentoo Handbook
Installation Docs

Documentation:
Home
Listing
About Gentoo
Philosophy
Social Contract

Resources:
Bug Tracker
Developer List
Discussion Forums
Gentoo BitTorrents
Gentoo Linux Enhancement Proposals
IRC Channels
Mailing Lists
Mirrors
Name and Logo Guidelines
Online Package Database
Security Announcements
Staffing Needs
Supporting Vendors
View our CVS

Graphics:
Logos and themes
Icons
ScreenShots

Miscellaneous Resources:
Gentoo Linux Store
Gentoo-hosted projects
IBM dW/Intel article archive




List Archive: gentoo-dev
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-dev@g.o
From: Joe Peterson <lavajoe@g.o>
Subject: Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
Date: Mon, 15 Dec 2008 15:43:11 -0700
Donnie Berkholz wrote:
> On 15:35 Mon 01 Dec     , Joe Peterson wrote:
>> 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.
> 
> Based on the rarity of me seeing this reported as a problem, I'm 
> inclined to think it says more about this user than about our system.

This could very-well be.  However:

> I don't think it's our responsibility to put documentation everywhere 
> someone might conceivably look for information.

I agree with this statement, but I wasn't implying we should duplicate
information everywhere.  I wanted to explore this as an opportunity to
re-think if having an official "de facto" spot for "gentoo readmes"
would make sense, thereby saving log output in a useful place where
users would learn to look regularly.  I agree this would only be
reasonable if it were the right thing, architecturally, for Gentoo, not
just for this one user's issue.

						-Joe


Replies:
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Duncan
References:
[RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Joe Peterson
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Gilles Dartiguelongue
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Joe Peterson
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Donnie Berkholz
Navigation:
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
Next by thread:
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
Previous by date:
Last Rites: app-portage/udept
Next by date:
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official


Updated Jun 17, 2009

Donate to support our development efforts.

Gentoo Centric Hosting: vr.org

VR Hosted

Tek Alchemy

Tek Alchemy

SevenL.net

SevenL.net

php|architect

php|architect

Copyright 2001-2007 Gentoo Foundation, Inc. Questions, Comments? Email www@gentoo.org.