| 1 |
On Fri, 2005-07-08 at 21:56 -0400, Allan Gottlieb wrote: |
| 2 |
> At Fri, 08 Jul 2005 12:47:51 -0500 kashani <kashani-list@××××××××.net> wrote: |
| 3 |
> |
| 4 |
> > Ron Bickers wrote: |
| 5 |
> >> On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: |
| 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 |
> . It would be nice to at |
| 13 |
> >> least have these messages logged somewhere. Are they? Can they be |
| 14 |
> >> without patching portage? |
| 15 |
> >> |
| 16 |
> > mkdir /var/log/portage |
| 17 |
> > echo "PORT_LOGDIR=/var/log/portage" >> /etc/make.conf |
| 18 |
> |
| 19 |
> Although I didn't check this particular case, it is normally true that |
| 20 |
> emerge generates *two* logs in the directory for each build. The |
| 21 |
> large one contains the normal stuff (e.g., compiler output); the small |
| 22 |
> one contains the important tidbits such as those mentioned above. |
| 23 |
|
| 24 |
Yes.. I have this set-up as well, however the caveat here is that this |
| 25 |
will be _after_ the fact. Hence, to me, it's largely useless. |
| 26 |
|
| 27 |
Roy Wright has written a nice util which does do nice things, |
| 28 |
essentially just grepping the ebuild files for einfo lines and putting |
| 29 |
it onto the screen. nice. |
| 30 |
|
| 31 |
-- |
| 32 |
Ow Mun Heng |
| 33 |
Gentoo/Linux on DELL D600 1.4Ghz 1.5GB RAM |
| 34 |
98% Microsoft(tm) Free!! |
| 35 |
Neuromancer 09:41:41 up 2 days, 17:38, 2 users, load average: 0.29, |
| 36 |
0.55, 0.57 |
| 37 |
|
| 38 |
|
| 39 |
-- |
| 40 |
gentoo-user@g.o mailing list |
Archives