| 1 |
Ron Bickers wrote: |
| 2 |
|
| 3 |
>On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: |
| 4 |
> |
| 5 |
> |
| 6 |
> |
| 7 |
>>Which is a huge bummer since most of us don't go checking the ebuilds |
| 8 |
>>for these specific lines. How I wish It would just abort and BLAST the |
| 9 |
>>Einfo on the screen for me to see the next day and decide to do it |
| 10 |
>>manually. |
| 11 |
>> |
| 12 |
>> |
| 13 |
> |
| 14 |
>I have this concern as well. Also, when emerging multiple packages, the |
| 15 |
>helpful and sometimes necessary output at the end of each merge is easily |
| 16 |
>missed as the next package begins. It would be nice to at least have these |
| 17 |
>messages logged somewhere. Are they? Can they be without patching portage? |
| 18 |
> |
| 19 |
> |
| 20 |
> |
| 21 |
Hi, |
| 22 |
Using two tools to handle this. |
| 23 |
First is "enotice"-tool, search for it don't have the link now. |
| 24 |
Second as was already mentioned is: PORTLOG_DIR in make.conf. |
| 25 |
PS: their functions are overlapping but just in case ;) |
| 26 |
HTH. Rumen |
Archives