From: "Joseph Booker" <joe@neoturbine.net>
To: gentoo-portage-dev@lists.gentoo.org
Subject: Re: [gentoo-portage-dev] Re: a suggestion about einfo messages
Date: Thu, 22 Jul 2004 15:48:09 -0500 (CDT) [thread overview]
Message-ID: <33577.68.78.46.139.1090529289.squirrel@68.78.46.139> (raw)
In-Reply-To: <cdmn9d$9qd$1@sea.gmane.org>
On Wed, July 21, 2004 4:30 pm, Joel Konkle-Parker said:
> Michael Kohl wrote:
>> They are stored in the emerge logs:
>>
>> # PORT_LOGDIR is the location where portage will store all the logs it
>> # creates from each individual merge. They are stored as YYMMDD-$PF.log
>> PORT_LOGDIR=/var/log/emerge/
>
> What logs are these? I have a default setup, and the only log I see is
> /var/log/emerge.log, which doesn't contain any einfo or ewarn messages
> whatsoever.
>
uncomment PORT_LOGDIR in your make.conf
then emerge something
then youll get a /var/log/portage/*-packages*.log containing what they are
talking about
--
Joseph Booker
joe @ irc.neoturbine.net
jj110888 @ irc.freenode.net
--
gentoo-portage-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-07-22 20:48 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-21 8:22 [gentoo-portage-dev] a suggestion about einfo messages YiDa Chiang
2004-07-21 9:04 ` Michael Kohl
2004-07-21 15:29 ` Joseph Booker
2004-07-21 15:51 ` Michael Kohl
2004-07-21 16:15 ` Thomas de Grenier de Latour
2004-07-21 16:19 ` Michael Kohl
2004-07-21 16:01 ` Thomas de Grenier de Latour
2004-07-21 16:06 ` Joseph Booker
2004-07-21 21:30 ` [gentoo-portage-dev] " Joel Konkle-Parker
2004-07-22 20:48 ` Joseph Booker [this message]
2004-07-22 21:31 ` Joel Konkle-Parker
2004-07-23 9:08 ` Kumba
2004-07-23 11:32 ` Joel Konkle-Parker
2004-07-25 15:57 ` [gentoo-portage-dev] SSE2 and MMX2 use flags Roman Gaufman
2004-07-25 16:16 ` Marius Mauch
2004-07-25 18:06 ` Roman Gaufman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=33577.68.78.46.139.1090529289.squirrel@68.78.46.139 \
--to=joe@neoturbine.net \
--cc=gentoo-portage-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox