Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 147152 - Emerge warnings and notes (ewarn, enote) should be included in /var/log/emerge.log
Summary: Emerge warnings and notes (ewarn, enote) should be included in /var/log/emerg...
Status: RESOLVED DUPLICATE of bug 11359
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: [OLD] Core system (show other bugs)
Hardware: All All
: High enhancement (vote)
Assignee: Gentoo Linux bug wranglers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-11 02:37 UTC by Myrddin Emrys
Modified: 2006-09-11 03:12 UTC (History)
1 user (show)

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 Myrddin Emrys 2006-09-11 02:37:20 UTC
The emerge warnings and notes that are output after a successful emerge are very transient... there is no way (that I know of) to recover them at a later date. They can include important messages about manual steps needed to use a package, important changes, and other things that are important to know... and they are completely lost and unrecoverable if you emerge multiple packages at once.

I believe that emerge warnings and notes should by default output into the emerge.log.

Now, if someone has a better idea I'm all for it... that's just the first solution I thought of. If they were in the log, genlop could be enhanced with a command to list the notes and warnings given from the last compile, or at least you could go through the logfile yourself.

Pulling information directly from the ebuilds is insufficient to solve this problem, because the warnings and notes are conditional... which ones are displayed depend on your flags, what version you had before, and other conditional tests in the ebuild.

If I'm completely wrong, and there is somewhere this information is stored, please accept my apologies... and point me in the right direction please. :-)
Comment 1 Allen Brooker (AllenJB) 2006-09-11 02:41:01 UTC
Please read up on the ELOG functionaliy (/etc/make.conf.example has notes on this) introduced in portage 2.1 (which is now stable for everyone)
Comment 2 Jakub Moc (RETIRED) gentoo-dev 2006-09-11 02:41:15 UTC
I have such an excellent idea - you will read /etc/make.conf.example and use ELOG features.


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

*** This bug has been marked as a duplicate of 11359 ***
Comment 3 Myrddin Emrys 2006-09-11 03:12:54 UTC
Thank you for the info Allen. No thank you for the sarcasm Jakub. My request stands though... it should be enabled by default, not off by default (which it is since PORTAGE_ELOG_COMMAND is unset by default).

A line or two in the .example telling people what 'elog' is might also help... I read those lines, but they meant nothing to me so I skipped them. Perhaps:

# The ELOG settings tell the system what to do with emerge notifications and 
# warnings other than simply printing them to the console. It is recommended
# that you enable logging (PORTAGE_ELOG_SYSTEM="save").

There has to be at least a minimum of explanation within the file, or how will people know that it's a feature they want to learn about? The letters 'elog' are not in the manfile for portage or make.conf... without a way for users to look something up, I think the sarcasm is unwarrented.

Myrddin