Bug 24913

Summary:	more logging for emerge needed
Product:	Portage Development	Reporter:	Serge Matveev <sergem>
Component:	Enhancement/Feature Requests	Assignee:	Nicholas Jones (RETIRED) <carpaski>
Status:	RESOLVED DUPLICATE
Severity:	enhancement
Priority:	High
Version:	2.0
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

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