How can alerts during builds be captured?

[labrador]

Many times I've seen little alerts printed during the middle of a build.
They often have stars around the comment, and sometimes have
colored stars as well. For example, during 'emerge system' on a sparc
a comment appeared that I need a /dev/openprom and it supplied
instructions on how to create the nod properly. If I had not been looking
at the screen at that time (which most of us are not, during the
12 hour gentoo emerges), I would have missed the information.

I'm pretty certain that myself and many other gentoo users are missing
critical information that is appearing in the midst of package
building.

Is there not a log of such alerts during package building?

If there isn't does anyone have a suggestion on how to
intelligently log those alerts (I mean, other than redirecting
all output to a file)? Someone familiar with the portage
system might have some insight into this.

The alerts related to etc-update and rc-update usually appeat at the
end of the build and that is fine since it is still on the screen, but I'm
mainly concerned with the alerts and notices that appear
during the creation of other bits, perhaps dependancies.

[Pythonhead]

Someone posted a patch to emerge to mail all those info lines, but
it hasn't made it into the official version yet, I think.

In the meantime, I wrote a messy hack you can find called ehush.
Look in the link in my .sig

[labrador]

I'm not clear on how to ensure ehush will capture the stuff
I want.

I also bumped into another thread on this, which referred to this
bug report on the feature request:

https://bugs.gentoo.org/show_bug.cgi?id=11359

They don't seem to know anything about ehush.

I'm not interested in emailing the notices - I might not have
email set up or installed at the time I'm emerging.

I just want a log that has everything aside from the gcc, configure and install traces. This isn't for debugging why a build failed, but for getting the notices that otherwise float by in my absence. Scrolling back in the screen buffer, even in an xterm buffer, isn't an option.

I'm kinda surprised how universal the problem is and yet how few people actually notice the einfo/ewarn happening on their system. Many people have probably noticed the cases which are marked with colored stars and/or beeps, but there are more that are not.