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: Duncan <1i5t5.duncan@...>
Subject: Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
Date: Mon, 15 Dec 2008 23:40:10 +0000 (UTC)
Joe Peterson <lavajoe@g.o> posted 4946DD7F.80408@g.o,
excerpted below, on  Mon, 15 Dec 2008 15:43:11 -0700:

>> 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.

That suggests an interesting possibility to me.  Let's see if anyone else 
likes it.

What about some place on the web, maybe on packages, having a single 
location with all the standard messages, listed by package and version.  
I'm picturing a single reference location where someone can look up the 
package and see all the routine postinst messages, etc, that it spits 
out.  Perhaps treat metapackages such that they group together all the 
messages from the collected sub-packages.

Then when we (as users) think about a big upgrade, we can go and research 
just what sort of thing the package maintainers already anticipate, and 
can thus better prepare ourselves.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



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
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
-- Joe Peterson
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:
Automated Package Removal and Addition Tracker, for the week ending 2008-11-30 23h59 UTC
Previous by date:
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
Next by date:
Re: Last Rites: app-portage/udept


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.