> You've convinced me: I want to upgrade from 2.0 to 2.1. And I want to do
> it completely. (I've experienced many problems in the past with
probably involving the incompatible KDE 1 and KDE 2
> So first, I want to wipe 2.0 off my system completely. How do I do
> that? Is
This is absurd!!! Not to mention less than simple as you will have some
packages (lige perhaps my beloved Quanta) that do not start with K. You
would need to rpm -e all packages and most likely would end up doing no
deps... not only that but you might lose settings too.
The difficulties people had with KDE upgrades on mdk were universally
this.. upgrading a 7.1 (KDE 1x) system with 7.2 RPMS that were never meant
to be installed on a 7.1 system for reasons too numerous to list here. KDE
1.x libs are handled entirely differently from mdk 7.1 to 7.2.
Quote:> it sufficient to uninstall (rpm -e) all the kde packages?
It is highly irrational... I have been building KDE from cvs since last
year... there is nothing whatsoever to indicate such extreme meaures.
> Then, I want to install KDE2.1, notably the apps (especially koffice,
> knetwork (I think - kmail/knode/konqueror, etc) ). Can I do this by
> installing the appropriate RPMs (from where?) or should I get the sources
> and compile everything? (If the latter, how do I convince rpm that I have
> the resulting apps/libraries/etc. installed?) And will installing the rpms
> or compiled sources set up the config files, etc.?
Yeesh! Do as you like! If you get RPMs just be damn usre they are for mdk
7.2!!! If they are from cooker they will be glibc 2.2 and have other issues
and would need to be forced.. then would not run. I'm pretty sure there are
mdk 7.2 rpms on the kde server now. ftp://kde.org
As to which is better... compiling is a bit more effort and a lot more
time... but it's got some pretty cool results! You get a pris* package
and can hop over to public cvs and get new stuff too. If you compile then
leave your existing install as is! Follow the instructions for two kdes on
the KDE site and then... make the new file as indicated to drop in
$KDEDIR/bin to set up your environment. The reference to the
window-managers file is depricated... it is now a group of files in
/etc/X11/windowmanagers.d/. Make a new one for your new KDE and I suggest
you use a different $kdehome if you do not have KDE 2.1 on your rpm install.
Reboot and you have your bleeding edge KDE (mine's cvs with new cool
things) and you still have your default install in case you choke. I have
not run my default install except for a few days when I upgraded from mdk
7.1 to 7.2.
> Thanks for any help!
> Lloyd Sumpter
A member of the Quanta+ Web development team