From: "Dustin C. Hatch" <admiralnemo@dchweb.com>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: GCC upgrade script
Date: Wed, 25 Apr 2007 07:03:50 -0500 [thread overview]
Message-ID: <462F43A6.9060404@dchweb.com> (raw)
In-Reply-To: <pan.2007.04.25.09.07.46@cox.net>
[-- Attachment #1: Type: text/plain, Size: 2492 bytes --]
If you don't want the versions, as Duncan wrote, I would suggest that
you use eix. eix -I will provide a pretty-printed list of all the
packages installed on your system. Read its man page to find out how to
do custom formatting. You can have it print just the package name, the
category and package names, versions, use flags, etc. Once you get a
feel for its syntax, you shouldn't have any trouble getting the
information you need.
Be careful, though, to run update-eix before doing anything because eix
uses an index database, not the actual portage tree or data. If you
make any changes to your system, eix will not know it until you run
update-eix.
Dustin C. Hatch
http://www.dchweb.com
Duncan wrote:
> "Mark Haney" <mhaney@ercbroadband.org> posted
> 462E2157.5050606@ercbroadband.org, excerpted below, on Tue, 24 Apr 2007
> 11:25:11 -0400:
>
>
>> A while back, someone posted a command that I think pulled all the info
>> from 'emerge -eav world' into a nice neat package so that a GCC upgrade
>> can be done in smaller increments. Now, however, I can't seem to find
>> it in the archives, or in my stored list backup. Can someone throw me a
>> copy of that post or point me to the right one online?
>>
>
> emerge -pe world|grep /|cut -f2 -d"]"|sed "s/^ /=/"
>
> That'll give you a list of packages, with the versions, preceded by "="
> for each one, so emerge will give you exactly the same versions. You can
> redirect it to a file as necessary.
>
> If you want it without versions, so as to emerge the latest, it gets
> somewhat hairier, because the version strings are somewhat difficult to
> automatically delete without error. I usually just take the lazy way
> out, replacing that sed above with another cut, as so:
>
> emerge -pe world|grep /|cut -f2 -d"]"|cut -f2 -d" "
>
> That still leaves the versions. Then I open the redirect file in my
> favorite editor and use search and replace with prompt, playing with the
> search pattern and repeating until I get what I want. A regex pattern of
> -[-abcr.0-9]*$, replaced with <nothing> gets most of it, but leaves
> strings such as -alpha and -beta, which are easy enough to remove on
> either further searches or manually. Of course, it's possible to include
> those in the regex search pattern as well, and would be possible to then
> make that a sed command, but it's difficult to get exactly right, then
> remember, and easy enough to do in a decent editor, so that's what I do.
>
>
[-- Attachment #2: Type: text/html, Size: 3255 bytes --]
next prev parent reply other threads:[~2007-04-25 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-24 15:25 [gentoo-amd64] GCC upgrade script Mark Haney
2007-04-25 8:34 ` [gentoo-amd64] " Stefan Wimmer
2007-04-25 9:07 ` Duncan
2007-04-25 12:03 ` Dustin C. Hatch [this message]
2007-04-25 13:39 ` Bo Ørsted Andresen
2007-04-25 13:57 ` Wil Reichert
2007-04-25 14:48 ` Bo Ørsted Andresen
2007-04-25 13:29 ` Bo Ørsted Andresen
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=462F43A6.9060404@dchweb.com \
--to=admiralnemo@dchweb.com \
--cc=gentoo-amd64@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