Bruno Lustosa wrote:
>* Brett Campbell <[EMAIL PROTECTED]> [07-02-2003 00:33]:
>> take a close look and emerge will warn you that /etc needs updating... something
>along the lines of `emerg --help config` ... you know, `find /etc -iname
>'._cfg????_*'`
>
>I just ssh'd to it from work, and saw it had already finished.
This seems to be a recurring problem, I do the same thing regularly -
luckily without incident. A variant I've encountered, is to do a
large set of updates and to loose the messages from the first packages
built in the noise generated from the remainder of the build.
It would be nice if there was some way of receiving the messages
generated during build without having to be around to read them when
the build is happening. My initial thoughts go to some sort of
optional email notification, this could contain progressively more
information depending on the options selected. e.g.
level 0 - Effectively off, this is the default
level 1 - Just the messages generated by ebuild
level 2 - The full build log, as you would currently see from the
console
Thinking about it some more; it may be worth extending it a bit. How
about providing multiple output targets, each with its own level. The
initial targets would be, standard output or email. If you were going
to be at the console and wanted to see the output, you could put the
standard output level at 2 and leave the email level at 0 (off). But
if you were about to set a build off, and leave it to finish on it's
own, you could turn off standard output, while putting the email
notification level up to 1.
Comments?
Sam
--
[EMAIL PROTECTED] mailing list
