| 1 |
One of the problems w/ even this is that I don't have the time to watch |
| 2 |
really long emerges, so I might not even know that I've missed important |
| 3 |
information that I need to find in the ebuild. It'd be nice if emerge |
| 4 |
would, in addition to logging the info, re-display it at the conclusion |
| 5 |
of the merge so that I can simply scroll back to read it. |
| 6 |
|
| 7 |
Dan Noe wrote: |
| 8 |
|
| 9 |
> On Fri, Jul 30, 2004 at 10:34:23AM -0700, Ben Munat wrote: |
| 10 |
> |
| 11 |
>>Okay, here's a really basic question, but one that I've never gotten |
| 12 |
>>around to answering, nor have I found an answer in the docs/forums: |
| 13 |
>> |
| 14 |
>>During an emerge, often messages like "Don't ever do foo or your whole |
| 15 |
>>system will explode!!!" fly by and they are not in the emerge.log. Is |
| 16 |
>>there someplace to find these after the fact? |
| 17 |
>> |
| 18 |
>>I suppose I could dump the output into a file but that might get |
| 19 |
>>unwieldy on an long emerge. Seems like portage should have an emerge.log |
| 20 |
>>and an emerge.messages... |
| 21 |
> |
| 22 |
> |
| 23 |
> I often go digging for the ebuild itself, open it up in vim, and read the |
| 24 |
> einfo block at my leisure. I would prefer, however, a log or other file |
| 25 |
> that contained the einfo information. Anyone? |
| 26 |
> |
| 27 |
> On a side note, I wish everyone on the list a joyous System Administrator's |
| 28 |
> Day :) |
| 29 |
> |
Archives