1 |
On Tue, 16 Mar 2010 01:00:21 +0000, David W Noon wrote: |
2 |
|
3 |
> >As do the log files in $PORT_LOGDIR, they contain exactly the same |
4 |
> >output you would see in the terminal. |
5 |
> |
6 |
> Not quite. The sequence in which the ebuilds were run is lost when the |
7 |
> discrete logs are your only source of tracing through, although one |
8 |
> could attempt to reconstruct it using the timestamps in the file names |
9 |
> of the ebuild logs. |
10 |
|
11 |
genlop -l gives you that, in a more useful format. |
12 |
|
13 |
> They also do not contain the results of the "pretend |
14 |
> depclean" that occurs at the end of an emerge job. |
15 |
|
16 |
Do you means the autoclean? That never picks up anything here. I think it |
17 |
only will if you have an unclean system. |
18 |
|
19 |
>Moreover, they do |
20 |
> not contain the report of the number of configuration files that need |
21 |
> updating by. |
22 |
> cfg-update (or the like). |
23 |
|
24 |
You can get that at the end of any emerge command. |
25 |
|
26 |
Parsing all that information in one large email without missing anything |
27 |
important sounds like a nightmare. I prefer each warning in a separate |
28 |
mail that I can mark as read when I have dealt with that particular |
29 |
issue, but each to their own. |
30 |
|
31 |
|
32 |
-- |
33 |
Neil Bothwick |
34 |
|
35 |
I used to live in the real world, but I got evicted. |