Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 24913 - more logging for emerge needed
Summary: more logging for emerge needed
Status: RESOLVED DUPLICATE of bug 11359
Alias: None
Product: Portage Development
Classification: Unclassified
Component: Enhancement/Feature Requests (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Nicholas Jones (RETIRED)
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-07-20 12:56 UTC by Serge Matveev
Modified: 2011-10-30 22:35 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Serge Matveev 2003-07-20 12:56:48 UTC
I suppose, we all need more logging for emerge. Emerge must have ability to log
any 'einfo' messages at least. Right now I must look at the monitor (and prees
Ctrl-S) while emerging process or find through huge 'tee' logs. I wan to run
'emerge gnome' or 'emerge kde' and later read only _important_ information. 

Emerge must log any events/strings, except compile etc. output or (in minimal
case) einfo messages. 

Maybe need new '/etc/make-conf' variable? 

How about syslog support? Right now I can't simple modify einfo source for
append strings to /vat/log/emerge.log, because my portages works under sandbox.
OTOH, I can send any string to syslog. It's right thing and UNIX way, to use syslog.

Reproducible: Always
Steps to Reproduce:
Comment 1 Serge Matveev 2003-07-20 13:00:36 UTC
I ses at least 4 levels of logging:
1) Current
2) Current + einfo(n)/ewarn/eerror/esyslog messages
3) All except "build output" (compile, linking, install etc.)
4) All (tee analog)
Comment 2 SpanKY gentoo-dev 2003-07-20 14:17:41 UTC

*** This bug has been marked as a duplicate of 11359 ***