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: Ryan Hill <dirtyepic@g.o>
Subject: Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
Date: Sun, 30 Nov 2008 12:20:59 -0600
On Sun, 30 Nov 2008 10:11:49 -0700
Joe Peterson <lavajoe@g.o> wrote:

> Peter Volkov wrote:
> > Seems that we already have everything you dreamed about: 
> > 
> > http://www.gentoo.org/doc/en/handbook/handbook-x86.xml?part=3&chap=1#doc_chap4
> > 
> > Take a look at PORTAGE_ELOG_SYSTEM. It even can send that messages
> > by mail :)
> 
> This is all cool, indeed!  :)
> 
> I suspect, however, that most users have never played with these
> variables.  I think that saving this info in the portage db or making
> it more default/official in some way could be a great help.  The core
> problem is, I think, that many users do not know where to look when
> having trouble, so they may not even realize that what they need is in
> the log info.

How more official can you get?  :P  By default we do save the logs, and
we provide a complete logging facility that can even log to syslog,
mail them to you, or run arbitrary commands.  We link to the
build log on build failure.  We reprint all log messages at the end of
the emerge by default.  If the user ignores these, and doesn't read the
manual, then...

I think educating the user about systems we already have in place beats
adding new ones.


-- 
gcc-porting,                                      by design, by neglect
treecleaner,                              for a fact or just for effect
wxwidgets @ gentoo     EFFD 380E 047A 4B51 D2BD C64F 8AA8 8346 F9A4 0662
Attachment:
signature.asc (PGP signature)
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
-- Peter Volkov
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:
Re: [RFC] Saving package emerge output (einfo, elog, ewarn, etc.) somewhere official
Previous by date:
Re: [RFC] Moving HOMEPAGE out of ebuilds for the future
Next by date:
Re: [RFC] Moving HOMEPAGE out of ebuilds for the future


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.