At Fri, 08 Jul 2005 12:47:51 -0500 kashani <[EMAIL PROTECTED]> wrote:
> Ron Bickers wrote: >> On Fri July 8 2005 01:38 am, Ow Mun Heng wrote: >> >>>Which is a huge bummer since most of us don't go checking the ebuilds >>>for these specific lines. How I wish It would just abort and BLAST the >>>Einfo on the screen for me to see the next day and decide to do it >>>manually. >> I have this concern as well. Also, when emerging multiple packages, >> the helpful and sometimes necessary output at the end of each merge >> is easily missed as the next package begins. It would be nice to at >> least have these messages logged somewhere. Are they? Can they be >> without patching portage? >> > mkdir /var/log/portage > echo "PORT_LOGDIR=/var/log/portage" >> /etc/make.conf Although I didn't check this particular case, it is normally true that emerge generates *two* logs in the directory for each build. The large one contains the normal stuff (e.g., compiler output); the small one contains the important tidbits such as those mentioned above. allan -- [email protected] mailing list
