From: Peter Ruskin <Peter.Ruskin@dsl.pipex.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Heads-Up sys-lib/com_err breaks Apps
Date: Sat, 9 Jul 2005 12:21:50 +0100 [thread overview]
Message-ID: <200507091221.50691.Peter.Ruskin@dsl.pipex.com> (raw)
In-Reply-To: <42CEA218.5050907@cisco.com>
On Friday 08 July 2005 16:56, Roy Wright wrote:
> Here's a perl script to display the einfo lines of packages to
> be merged. Just run it with the same options you will use for
> emerge. Example:
>
> einfo -uDN world >einfo.txt
> emerge -uDN world
> less einfo.txt
>
> You will probably want to save the output to refer to after
> emerging.
>
> Enjoy,
> Roy
>
> #!/usr/bin/perl
>
> # this script will run emerge with the given command line options
> plus # "--pretend". It will then grep all of the packages to be
> merged looking # for einfo lines to display.
>
> $portage = '/usr/portage';
> $emerge = "emerge @ARGV --pretend";
>
> open(EMERGE, "$emerge|") || die "unable to open $emerge\n";
> while(<EMERGE>) {
> if(/\[[^\]]+\]\s+(\S+)\/(\S+)\-(\d\S*)\s/) {
> findInfo($1,$2,$3);
> }
> }
> close(EMERGE);
>
> exit 0;
>
> sub findInfo
> {
> local ($package,$name,$ver) = @_;
> local $pkgDir = "$portage/$package/$name";
> local $ebuild = "$pkgDir/$name-$ver.ebuild";
> print "$ebuild\n";
> if(-T $ebuild) {
> open(EBUILD, "<$ebuild") || warn "unable to read
> $ebuild\n"; while(<EBUILD>) {
> if(/(einfo.*)$/) {
> print " $1\n";
> }
if(/(ewarn.*)$/) {
print " $1\n";
}
if(/(eerror.*)$/) {
print " $1\n";
}
> }
> close(EBUILD);
> }
> print "\n";
> }
>
Thanks, nice script Roy. With the ewarn and eerror additions above
you get even more information.
I use the following in root's crontab:
# sync Gentoo nightly and check for updates
0 0 * * 1-6 /usr/sbin/esync -ns && /usr/bin/update-eix -q
&& /usr/bin/emerge world -uNvplt && /usr/local/bin/einfo -uN world
# sync Gentoo weekly and check (deep) for updates
0 0 * * 7 /usr/sbin/esync -ns && /usr/bin/update-eix -q
&& /usr/bin/emerge world -uNDvtpl && /usr/local/bin/einfo -uND
world
--
Peter
========================================================================
Gentoo Linux: Portage 2.0.51.19. kernel-2.6.12-gentoo.
i686 AMD Athlon(tm) XP 3200+. gcc(GCC): 3.3.5-20050130.
KDE: 3.4.1. Qt: 3.3.4.
========================================================================
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-07-09 11:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 5:38 [gentoo-user] Heads-Up sys-lib/ss breaks Apps Ow Mun Heng
2005-07-08 6:04 ` Zac Medico
2005-07-08 6:28 ` [gentoo-user] Heads-Up sys-lib/com_err " Ow Mun Heng
2005-07-08 7:11 ` Zac Medico
2005-07-08 7:38 ` W.Kenworthy
2005-07-08 7:53 ` Ow Mun Heng
2005-07-08 15:56 ` Roy Wright
2005-07-09 11:21 ` Peter Ruskin [this message]
2005-07-09 12:04 ` Peter Ruskin
2005-07-10 1:24 ` Roy Wright
2005-07-08 15:52 ` [gentoo-user] Heads-Up sys-lib/ss " Ron Bickers
2005-07-08 16:51 ` Uwe Thiem
2005-07-08 17:47 ` kashani
2005-07-09 1:56 ` Allan Gottlieb
2005-07-10 1:41 ` Ow Mun Heng
2005-07-08 19:17 ` Rumen Yotov
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=200507091221.50691.Peter.Ruskin@dsl.pipex.com \
--to=peter.ruskin@dsl.pipex.com \
--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