On Saturday 24 June 2006 18:05, James wrote: > One of the KDE devs should put out a tool or script to completely > nuke kde, then let folks run > emerge -uavDN kde-meta' and be done with it. Disk space is cheap > and I do not have time to 'hack' at kde across 7 workstations. > Re compiling everything from from scratch is no bid deal. Waisting > lots of timer, per machine to migrate from monolithic to meta > has wasted quite a lot of time, and I still have 6 more machines to go.
You seem to have been more confused than enlightened by the tricks I posted.
If you want to nuke kde completely you should just do:
# cd /var/db/pkg && emerge -Cva kde-base/*
It's as simple as that. Both Neil and I told you that a long time ago. This
nukes both new and old slots. Both split and monolithic. And allows you to
start with kde from scratch.
> So on the next machine, here's my steps to completely nuke kde
> install kde-meta:
>
> First:
[SNIP]
There is no reason call emerge 12 times. Just use one command:
# emerge --unmerge
kde-base/kde{,artwork,games,addons,webdev,admin,graphics,multimedia,pim,utils,edu,base,toys}
That changes nothing though (except you forgot to unmerge kde-base/kde - the
above command includes that too). And this is unnecessary if you nuked kde
completely.
> Second:
> <Now remove all old kde 3.2, 3.3, and 3.4 kruft>
> # cd /var/db/pkg && emerge -Cva kde-base/*-3.{2,3,4}*
That also is only necessary if you did not nuke kde completely.
> # env-update && source /etc/profile && etc-update && update-eix && eupdatedb
This is completely pointless after unmerging something.
> Third:
> <clean up broken links>
> # revdep-rebuild -p
> # revdep-rebuild
You can do that after emerging kde-meta-3.5. No reason to do it before.
> # emerge --sync
> # env-update && source /etc/profile && etc-update
Again this is completely pointless at this time.
> Fourth:
> <install kde-meta>
> emerge -uavDNp kde-meta
> <if blocking occurs, unmerge clocking packages and return to Second>
> emerge -uavDN kde-meta
Blocking won't occur if you already removed the monolithic packages.
> Did I miss anything? Did I get anything out of order?
> Please edit to make this a mechanical process, or add in
> options at the right place to go the selection of
> individual kde packages after installing kdebase-meta?
Now you should run revdep-rebuild. You need to make up your mind if you want
to nuke everything or not. You keep saying you want to nuke kde completely
and yet follow advice that avoids nuking it completely. Assuming you really
do want to nuke kde completely (on your other computers):
# cd /var/db/pkg && emerge -Cva kde-base/*
# emerge -uva kde-meta
# revdep-rebuild -p
# revdep-rebuild
--
Bo Andresen
pgpRNucQwdQLY.pgp
Description: PGP signature
