> Basically, it could be implemented using a new eclass or just adding the
> enotice function to eutils - I wouldn't want all the einfos logged,
> anyway. (patching notices? no thanks.)

> What I would like, would be messages from packages like cacti.
> enotice itself will write into the file and emit an einfo.

I mentioned what I would consider most acceptable at some point,
but no one appears to have seen that, so it must have gotten lost.

He's what needs to get done for this to work:

functions.sh (from baselayout) dependence needs to go away.
All used functions need to be logged/rewritten to not use those
functions, and instead maintain its own.

All said functions must be rewritten, for portage, with the
capability to handle colors and terminals and the like as
portage does currently. (People don't want ANSI in their logs.)

The output can be writting in any number of ways to a file in
${T} during the execution of the build. This does not violate
sandbox and is quite easy to find.

PORTAGE can then manipulate the log, perform notifications,
and do whatever else is necessary to maintain that file around
cleanings and other merges.

${T}/notices.${PF}.${TYPE}
would be perfectly fine as long as it was definitive/unique
to the particular package. Notices of all types could also
simply be prefixed. '*' '-' '!' or whatever seems best.

If you are so inclined, you could also write a parser for
these files that can designate priorities using color or
some other visual aid. (Keep in mind that it must be
deterministic through simple ascii as well for synthesisers.)
For multiple reasons, I prefer python for these tools.

There are many, many possibilities, but please follow
the outline provided here.

--NJ