unmerging slotted group packages

I discovered by accident that I have KDE 3.3, 3.4, & 3.5
all installed
at the same time.
I wanted to clean out 3.3 (at least) and tried emerge -aC
=kde-base/kde-3.3.0 which of course just did this pseudo
package, not
the containing packages.
I also tried emerge --clean kde-base/kde but this says
nothing to
remove, even though 3.4 & 3.5 are still present:
[D] kde-base/kde
     Available versions:  (3.5)  3.5.2 3.5.5
     Installed:           3.4.3(3.4)(17:19:35
01/18/06)(-accessibility)
                          3.5.5(3.5)(02:50:53
12/10/06)(-accessibility)
     Homepage:            http://www.kde.org/
     Description:         KDE - merge this to pull in all
non-developer kde-base/* packages

I got rid of 3.3 by doing eix -I kde & removing each
sub-package
manually, I just think I must be missing an easier way.
-- 
gentoo-amd64gentoo.org mailing list

On Sun, 28 Jan 2007 16:17:37 +1100, Daiajo Tibdixious
wrote:

> I discovered by accident that I have KDE 3.3, 3.4,
& 3.5 all installed
> at the same time.
> I wanted to clean out 3.3 (at least) and tried emerge
-aC
> =kde-base/kde-3.3.0 which of course just did this
pseudo package, not
> the containing packages.

> I got rid of 3.3 by doing eix -I kde & removing
each sub-package
> manually, I just think I must be missing an easier
way.

eix -A kde-base -Icn | awk '/kde-base/ {print $2}' | xargs
emerge --Prune --pretend

Then remove --pretend when you are satisfied with what it
wants to remove.


-- 
Neil Bothwick

Employ teenagers - while they know everything.

On Sunday 28 Jan 2007, Daiajo Tibdixious wrote:

> I got rid of 3.3 by doing eix -I kde & removing
each sub-package
> manually, I just think I must be missing an easier
way.

Looks like you could just have waited for Paludis to arrive
(see the latest 
GWN).

-- 
Rgds
Peter
-- 
gentoo-amd64gentoo.org mailing list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Peter Humphrey wrote:
> On Sunday 28 Jan 2007, Daiajo Tibdixious wrote:
> 
>> I got rid of 3.3 by doing eix -I kde & removing
each sub-package
>> manually, I just think I must be missing an easier
way.
> 
> Looks like you could just have waited for Paludis to
arrive (see the latest 
> GWN).
> 

Is anybody actually using this on amd64?  It looks
interesting but
they've had about 6 releases in the last 30 days.  I'm also
not sure how
much of an official blessing it has.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


iD8DBQFFvI8VG4/rWKZmVWkRAgZ4AKCewBXRTV8Re0Pf7L8ZTPmCF30hXACg
lsRc
J81jbE2dHYaxLRU2fitKgjI=
=VSuJ
-----END PGP SIGNATURE-----

On Sunday 28 Jan 2007, Richard Freeman wrote:

> Is anybody actually using [paludis] on amd64?  It looks
interesting but
> they've had about 6 releases in the last 30 days.  I'm
also not sure how
> much of an official blessing it has.

I thought I'd give it a spin, but then I thought better of
it when I saw the 
extent the developers have gone to to deter us from
experimenting yet, so 
I've ditched it for now.

-- 
Rgds
Peter
-- 
gentoo-amd64gentoo.org mailing list

Both suggestions sound good. I did read about Paludis but
still sounds
like vapourware. :(
--prune sounded scary in the man page for emerge.
I also need to learn awk, heard about it, never used it,
looks cool,
it produces precisely the action I wanted, thanks.

On 1/28/07, Peter Humphrey <prhgotadsl.co.uk> wrote:
> On Sunday 28 Jan 2007, Daiajo Tibdixious wrote:
>
> > I got rid of 3.3 by doing eix -I kde &
removing each sub-package
> > manually, I just think I must be missing an easier
way.
>
> Looks like you could just have waited for Paludis to
arrive (see the latest
> GWN).
>
> --
> Rgds
> Peter
> --
> gentoo-amd64gentoo.org mailing list
>
>
-- 
gentoo-amd64gentoo.org mailing list

Duncan:  Yet another great document about keeping a Gentoo
system up to 
date.  I looked at the Gentoo Wiki site to see if they had
anything
similar and the closest was the HOWTO Maintain
Gentoo-Best_Practices
article:

http://gentoo-wiki.com/HOWTO_Maintain_Gentoo_
-_%22Best_Practices%22

It would be nice if some of your material could be added to
it because
your comments are good help for all Gentoo people..

Thank you,

Steve Herber	herberthing.com		work: 206-221-7262
Security Engineer, UW Medicine, IT Services	home:
425-454-2399

-- 
gentoo-amd64gentoo.org mailing list

Replying to Duncan,
Thanks, very informative. I've been doing everything except
for
--depclean, as that has never worked. Now I see that it is
because of
kde-3.4 which was built with samba (which I have now
removed) and a
version of qt that is no longer there.

I used Neil's awk command to remove kde-3.4 and now
--depclean works.

I have now more than 130 orphaned packages. After removing a
lot of
gnome related items (I've never run gnome on this system)
and a lot of
other things I recognised, I still have more than 130
orphaned
packages, even tho the number of installed packages went
from 608 to
563!
This could take a while, especially as revdep-rebuild is
complaining a
lot about stuff I've removed.

BTW
FEATURES="buildpkg parallel-fetch fixpackages"
-- 
gentoo-amd64gentoo.org mailing list

On Mon, 29 Jan 2007 10:48:28 +1100, Daiajo Tibdixious
wrote:

> I have now more than 130 orphaned packages. After
removing a lot of
> gnome related items (I've never run gnome on this
system) and a lot of
> other things I recognised, I still have more than 130
orphaned
> packages, even tho the number of installed packages
went from 608 to
> 563!
> This could take a while, especially as revdep-rebuild
is complaining a
> lot about stuff I've removed.

This is to be expected if you remove only some of the
packages listed by
depclean, as other packages in the list may depend on them.
This is
because revdep-rebuild works with installed files not the
package list.

Wait until you have removed everything in the list before
running
revdep-rebuild and then emerge -uavDN world.


-- 
Neil Bothwick

Maybe... How much are you bribing me this time?

ON MONDAY 29 JANUARY 2007 13:03:28 DUNCAN WROTE:
> WHILE I KNEW THAT WORLD DOESN'T CONTAIN SLOTS
> OR VERSIONS, I THOUGHT (AND BELIEVE IT WORKS THAT WAY
IN ~PORTAGE, BUT IT
> MAY NOT HAVE REACHED STABLE YET, AND I COULD BE WRONG)
THAT UNMERGING THE
> METAPACKAGE WOULD THEN RELEASE THE DEPENDENCY ON THE
OTHER STUFF IN THAT
> SLOT.  FOR KDE MONOLITHICS, FOR INSTANCE, I BELIEVE(D)
THAT WHILE
> OLD KDELIBS WON'T BE UNMERGED IMMEDIATELY AS IT
ISDEPENDED ON BY
> KDEBASE WHICH IS DEPENDED ON BY (AMONG OTHERS)
KDEGRAPHICS, WITHOUT THE
> OLD KDE-3.4.X, KDEGRAPHICS-3.4.X WOULD BE TRIMMED BY
--DEPCLEAN, AND ONCE
> ALL THE OTHER KDEWHATEVER-3.4.X PACKAGES HAD BEEN
TRIMMED, THEN
> KDEBASE-3.4.X COULD BE TRIMMED, AND THEN KDELIBS-3.4.X

NOPE. AND IT'S NOT GOING TO CHANGE ANYTIME SOON. A SAFER
--PRUNE, HOWEVER, 
DOES HAVE A GOOD CHANCE OF GOING INTO PORTAGE 2.1.3 (TO FIX
BUG #151653).

> HOWEVER, I'M USING THE SPLIT PACKAGES, NOT THE
MONOLITHICS, AND DON'T HAVE
> KDE-META MERGED AS I DON'T NEED ALL THE SPLIT PACKAGES
EITHER.

DOESN'T REALLY MAKE A DIFFERENCE. THE MOST BASIC DEPS (ARTS
AND KDELIBS) DON'T 
DIFFER AT ALL. THE PROBLEM WITH USING KDE AS A TEST CASE IS
THAT KDE-3.4 LEFT 
THE TREE 4 MONTHS AGO... ;)

-- 
BO ANDRESEN