| 1 |
On Saturday 24 June 2006 18:05, James wrote: |
| 2 |
> One of the KDE devs should put out a tool or script to completely |
| 3 |
> nuke kde, then let folks run |
| 4 |
> emerge -uavDN kde-meta' and be done with it. Disk space is cheap |
| 5 |
> and I do not have time to 'hack' at kde across 7 workstations. |
| 6 |
> Re compiling everything from from scratch is no bid deal. Waisting |
| 7 |
> lots of timer, per machine to migrate from monolithic to meta |
| 8 |
> has wasted quite a lot of time, and I still have 6 more machines to go. |
| 9 |
|
| 10 |
You seem to have been more confused than enlightened by the tricks I posted. |
| 11 |
If you want to nuke kde completely you should just do: |
| 12 |
|
| 13 |
# cd /var/db/pkg && emerge -Cva kde-base/* |
| 14 |
|
| 15 |
It's as simple as that. Both Neil and I told you that a long time ago. This |
| 16 |
nukes both new and old slots. Both split and monolithic. And allows you to |
| 17 |
start with kde from scratch. |
| 18 |
|
| 19 |
> So on the next machine, here's my steps to completely nuke kde |
| 20 |
> install kde-meta: |
| 21 |
> |
| 22 |
> First: |
| 23 |
[SNIP] |
| 24 |
|
| 25 |
There is no reason call emerge 12 times. Just use one command: |
| 26 |
|
| 27 |
# emerge --unmerge |
| 28 |
kde-base/kde{,artwork,games,addons,webdev,admin,graphics,multimedia,pim,utils,edu,base,toys} |
| 29 |
|
| 30 |
That changes nothing though (except you forgot to unmerge kde-base/kde - the |
| 31 |
above command includes that too). And this is unnecessary if you nuked kde |
| 32 |
completely. |
| 33 |
|
| 34 |
> Second: |
| 35 |
> <Now remove all old kde 3.2, 3.3, and 3.4 kruft> |
| 36 |
> # cd /var/db/pkg && emerge -Cva kde-base/*-3.{2,3,4}* |
| 37 |
|
| 38 |
That also is only necessary if you did not nuke kde completely. |
| 39 |
|
| 40 |
> # env-update && source /etc/profile && etc-update && update-eix && eupdatedb |
| 41 |
|
| 42 |
This is completely pointless after unmerging something. |
| 43 |
|
| 44 |
> Third: |
| 45 |
> <clean up broken links> |
| 46 |
> # revdep-rebuild -p |
| 47 |
> # revdep-rebuild |
| 48 |
|
| 49 |
You can do that after emerging kde-meta-3.5. No reason to do it before. |
| 50 |
|
| 51 |
> # emerge --sync |
| 52 |
> # env-update && source /etc/profile && etc-update |
| 53 |
|
| 54 |
Again this is completely pointless at this time. |
| 55 |
|
| 56 |
> Fourth: |
| 57 |
> <install kde-meta> |
| 58 |
> emerge -uavDNp kde-meta |
| 59 |
> <if blocking occurs, unmerge clocking packages and return to Second> |
| 60 |
> emerge -uavDN kde-meta |
| 61 |
|
| 62 |
Blocking won't occur if you already removed the monolithic packages. |
| 63 |
|
| 64 |
> Did I miss anything? Did I get anything out of order? |
| 65 |
> Please edit to make this a mechanical process, or add in |
| 66 |
> options at the right place to go the selection of |
| 67 |
> individual kde packages after installing kdebase-meta? |
| 68 |
|
| 69 |
Now you should run revdep-rebuild. You need to make up your mind if you want |
| 70 |
to nuke everything or not. You keep saying you want to nuke kde completely |
| 71 |
and yet follow advice that avoids nuking it completely. Assuming you really |
| 72 |
do want to nuke kde completely (on your other computers): |
| 73 |
|
| 74 |
# cd /var/db/pkg && emerge -Cva kde-base/* |
| 75 |
# emerge -uva kde-meta |
| 76 |
# revdep-rebuild -p |
| 77 |
# revdep-rebuild |
| 78 |
|
| 79 |
-- |
| 80 |
Bo Andresen |
Archives