[gentoo-amd64] GCC upgrade script

[gentoo-amd64] GCC upgrade script

[Mark Haney]

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?

TIA.

-- 
Ita erat quando hic adveni.

Mark Haney
Sr. Systems Administrator
ERC Broadband
(828) 350-2415
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: GCC upgrade script

[Stefan Wimmer]

* Mark Haney <mhaney@ercbroadband.org> [2007-04-24 15:25] :
>  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?

The only thing that comes to (my very tired) mind is emwrap.sh ... you 
should be able to find all available information at 
http://forums.gentoo.org/viewtopic-t-282474.html 

HTH
Stefan

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: GCC upgrade script

[Duncan]

"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.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: GCC upgrade script

[Dustin C. Hatch]

[-- 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 --]

Re: [gentoo-amd64] Re: GCC upgrade script

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 520 bytes --]

On Wednesday 25 April 2007 11:07:46 Duncan wrote:
> emerge -pe world|grep /|cut -f2 -d"]"|sed "s/^ /=/"

This might work reasonably had you included -q for emerge.. As it is it may 
include things like e.g. USE="blah%" (which emerge would choke on)...

# emerge -peq world | sed -n 's|^\[ebuild[^]]*\] \([^ ]\+\).*$|=\1|p'

> emerge -pe world|grep /|cut -f2 -d"]"|cut -f2 -d" "

# emerge -peq world | sed -n 's|^\[ebuild[^]]*\] \([^ ]\+\).*$|\1|p' | \
    sed -r 's/-[^-]+(-r[0-9]+)*$//'

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] Re: GCC upgrade script

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 818 bytes --]

On Wednesday 25 April 2007 14:03:50 Dustin C. Hatch wrote:
> 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.

The big difference between the last command in my previous response to this 
thread and an eix command like:

# eix -nI --format '<category>()/<name>()' | \
    grep -v '^$\|^Found\ [0-9]*\|^\[[0-9]*\]'

is that the eix command will include all installed packages (including those 
that would show up if you run emerge --depclean -p) whereas the emerge 
command will only show packages that are either in world or a dependency of a 
package in world (direct or indirect). --with-bdeps (see `man emerge`) also 
affects the emerge package list.

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-amd64] Re: GCC upgrade script

[Wil Reichert]

On 4/25/07, Bo Ørsted Andresen <bo.andresen@zlin.dk> wrote:
> On Wednesday 25 April 2007 14:03:50 Dustin C. Hatch wrote:
> > 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.
>
> The big difference between the last command in my previous response to this
> thread and an eix command like:
>
> # eix -nI --format '<category>()/<name>()' | \
>     grep -v '^$\|^Found\ [0-9]*\|^\[[0-9]*\]'
How about just:

# qlist -IC

but if you wanna hit all the packages in your system then you really
want the version info there.  My fav is:

# for package in `qlist -IvC | grep 9999`; do emerge -1 =$package; done

because live packages don't know if they need to be updated or not.

Wil
--
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] Re: GCC upgrade script

[Bo Ørsted Andresen]

[-- Attachment #1: Type: text/plain, Size: 658 bytes --]

On Wednesday 25 April 2007 15:57:58 Wil Reichert wrote:
> > # eix -nI --format '<category>()/<name>()' | \
> >     grep -v '^$\|^Found\ [0-9]*\|^\[[0-9]*\]'
>
> How about just:
>
> # qlist -IC

Same output but obviously a lot easier syntax wise.

> but if you wanna hit all the packages in your system then you really
> want the version info there.

Indeed. If you strip the versions then you'll reemerge the latest slot of 
packages like automake and db once per installed slot while the previous 
slots won't get remerged at all.

Also my comment about --with-bdeps obviously doesn't apply when --emptytree is 
used.

-- 
Bo Andresen

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]