Important emerge messages disappearing before I can read.

[jjolly]

Hi all,

I've had a problem with the useful (and sometimes vital) emerge post-install messages flying past on the screen. Is is especially prevalent when doing 'emerge -u world'. I have made a habit of doing 'emerge -up world' and emerging each package one at a time from top to bottom, but this is horribly time consuming (and really doesn't work well in a cron job ).

So, my question: Is something in place that would allow me to view those messages after a long emerge session? Certainly not /var/log/emerge.log since that only shows that an emerge was done, none of the relevant message.

Just making sure the work isn't already done.
_________________
John Jolly
"Of all the things I've lost, I miss my mind the most."

[bsolar]

You can redirect the output of emerge to a file.

[jjolly]

Thanks, not only do I now know how to catch those messages, but I have also be introduced to a new (to met, at least) tool.

Is there any reason why this isn't in the scripts to begin with? Much like a --logfile (-l) option. Or why not add it to the make.conf as a LOGFILE= variable.

I'm sure I could go on and on with the feature request. Anybody mind if I add it?
_________________
John Jolly
"Of all the things I've lost, I miss my mind the most."

[AndiW]

Another method is to start your emerge with:

[BlackBart]

or emerge portage then update your make.conf and there is an option to specify where you want your emerge logs to go.