| 1 |
On Mon, 2002-06-10 at 11:01, Alexander Holler wrote: |
| 2 |
> Hi, |
| 3 |
> |
| 4 |
> --On Sonntag, Juni 09, 2002 23:17:33 -0700 George Shapovalov |
| 5 |
> <georges@×××××××××××.edu> wrote: |
| 6 |
> |
| 7 |
> > It should be easy to call it inside the script you use to emerge packages |
| 8 |
> > on this server. If you desire to make reports on a per-package basis it |
| 9 |
> > should be easy to create the script that would run emerge --pretend |
| 10 |
> > packagename first and then call emerge for every reported package and |
| 11 |
> > capture reports separately... |
| 12 |
> > WTF incorporating this into portage itself: I did not see this mentioned |
| 13 |
> > (though there were some related things suggested). If you think this is |
| 14 |
> > an important addition please file a feature request to bugs.gentoo.org. |
| 15 |
> |
| 16 |
> I would find it useful too, if warnings, comments and so on would be |
| 17 |
> displayed and/or logged separately. Emerge could display those warnings at |
| 18 |
> the end of the whole process (e.g. update world). So none would be getting |
| 19 |
> lost in the mass. |
| 20 |
|
| 21 |
The position of these warnings in the build output is sometimes |
| 22 |
important, and it seems that splitting the build output could lose |
| 23 |
information. A simple search in the log could point you to the warnings, |
| 24 |
errors or anything. Anyway, it may be interesting to have an option to |
| 25 |
show only the output warnings/errors/etc. in the interactive output. |
Archives