From: "John Dangler" <jdangler@atlantic.net>
To: <gentoo-user@lists.gentoo.org>
Subject: RESOLVED: [gentoo-user] emerge output
Date: Fri, 26 Aug 2005 11:49:53 -0400 [thread overview]
Message-ID: <01dc01c5aa55$df7b77c0$0501a8c0@croatus> (raw)
In-Reply-To: <20050826083301.GB23152@lisa.tutaj>
Neil, Mariusz~
Thanks for the input. Just setting up PORT_LOGDIR has gone a long way to
providing exactly what I'm looking for. It's a shame that this isn't setup
by default, but I can think of a few reasons why it isn't.
John D
-----Original Message-----
From: Mariusz Pêkala [mailto:skoot@qi.pl]
Sent: Friday, August 26, 2005 4:33 AM
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] emerge output
On 2005-08-26 01:48:36 +0200 (Fri, Aug), Holly Bostick wrote:
> Idea #3: there is a way (and possibly more than one) to tail out the
> einfo messages, either to a file, or to the console, but unfortunately I
> don't remember what they are atm.... Oh, wait, they're listed on the Wiki:
>
> http://gentoo-wiki.com/TIP_Portage_utilities_not_in_portage
>
> I think what you might want is portlog-info, which is in the
> Informational Utilities section.
...or something dumber^H^H^H^H^Hsimpler:
# ---------------------------------------
#!/bin/bash
COUNT=60
cd /var/log/portage || exit -1
for file in $( ls -1rt | tail -n $COUNT)
do
if grep $'\e' "$file" | grep -q -v -e " Applying [^ ]*.patch" -e
$'\e'"\[32;01mok"$'\e'"\[34;01m"
then
tput bold
echo ' ----------------------------------------------------'
ls -l "$file"
echo ' ----------------------------------------------------'
tput sgr0
grep $'\e' "$file" | grep -v " Applying [^ ]*.patch"
fi
done
# ---------------------------------------
The log files are created when you set the PORT_LOGDIR in /etc/make.conf
(yeah, you replace then that "cd /var/log/portage" with your - possibly
different - location, or do something like eval $(grep "^PORT_LOGDIR="
/etc/make.conf)) .
HTH
--
No virus found in this outgoing message.
Checked by 'grep -i virus $MESSAGE'
Trust me.
--
gentoo-user@gentoo.org mailing list
prev parent reply other threads:[~2005-08-26 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 23:01 [gentoo-user] emerge output John Dangler
2005-08-25 23:48 ` Holly Bostick
2005-08-26 0:27 ` Tony Davison
2005-08-26 7:49 ` Neil Bothwick
2005-08-26 8:33 ` Mariusz Pękala
2005-08-26 15:49 ` John Dangler [this message]
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='01dc01c5aa55$df7b77c0$0501a8c0@croatus' \
--to=jdangler@atlantic.net \
--cc=gentoo-user@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