| 1 |
Alan Mackenzie wrote: |
| 2 |
> |
| 3 |
> Hmmm. Yes. The problem is not so much the reading, but that the |
| 4 |
> pertinent text is only fleetingly on the screen. I'm quite sure I saw |
| 5 |
> these warnings, but their seriousness didn't impinge on my consciousness. |
| 6 |
> Sadly. |
| 7 |
> |
| 8 |
> Are these warnings stored in a log anywhere? Looking for them in ebuilds |
| 9 |
> before emerging would be a bit tedious. |
| 10 |
> |
| 11 |
> Or maybe it needs a script which would take the output of "emerge -puND |
| 12 |
> world", extract the ebuild names, and run them through "grep ewarn". Or |
| 13 |
> does such already exist? |
| 14 |
> |
| 15 |
> |
| 16 |
|
| 17 |
There are tools for that: |
| 18 |
|
| 19 |
root@fireball / # eix app-portage/elog |
| 20 |
[I] app-portage/elogv |
| 21 |
Available versions: 0.7.4{tbz2} ~0.7.4-r1 |
| 22 |
Installed versions: 0.7.4{tbz2}(02:43:28 PM 05/17/2011) |
| 23 |
Homepage: http://gechi-overlay.sourceforge.net/?page=elogv |
| 24 |
Description: Curses based utility to parse the contents of |
| 25 |
elogs created by Portage |
| 26 |
|
| 27 |
[I] app-portage/elogviewer |
| 28 |
Available versions: 0.5.2-r2{tbz2} ~0.6.1 ~0.6.2 ~0.6.2-r1 |
| 29 |
Installed versions: 0.5.2-r2{tbz2}(04:17:22 PM 05/17/2011) |
| 30 |
Homepage: http://sourceforge.net/projects/elogviewer/ |
| 31 |
Description: GTK+ based utility to parse the contents of |
| 32 |
elogs created by Portage |
| 33 |
|
| 34 |
Found 2 matches. |
| 35 |
root@fireball / # |
| 36 |
|
| 37 |
That should help. I liked it when all the messages like that were saved |
| 38 |
until the end of the emerge then displayed. I rarely sit and watch for |
| 39 |
the stuff scroll by anymore. |
| 40 |
|
| 41 |
Dale |
| 42 |
|
| 43 |
:-) :-) |
Archives