Very Computer

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

   So first, I want to wipe 2.0 off my system completely. How do I do that? Is
it sufficient to uninstall (rpm -e) all the kde packages?

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

Thanks for any help!
Lloyd Sumpter

i am a new, but will tell how i did.

i downloaded the stable version, including all qt lib's(2.2.4)

this took several days because of dial up connection.

the i open the rpm manager and selected the upgrade. i beleive it replaced

the old kde 2.0 and old qt libraries.  the kdevelop never would work until

i upgraded and it now works.

i had originally decided to wipe it all out and start from scratch, but
decided to

try the upgrade first, so far it is working great. i do have to repair the
kppp

connection, but i have done it before.

hope it helps.

macom

Quote:> 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 "upgrades").

>    So first, I want to wipe 2.0 off my system completely. How do I do
that? Is
> it sufficient to uninstall (rpm -e) all the kde packages?

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

> Thanks for any help!
> Lloyd Sumpter

-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----==  Over 80,000 Newsgroups - 16 Different Servers! =-----

probably involving the incompatible KDE 1 and KDE 2

Quote:

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

Quote:

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

Enjoy

Quote:

> Thanks for any help!
> Lloyd Sumpter

--

A member of the Quanta+ Web development team
http://www.veryComputer.com/

   As I said, I've had many problems "upgrading" packages: not KDE
specifically, but in general. And one thing I'm pedantic about: I like my
HD CLEAN. I hate having 5 different versions of things lying around, having
libs I don't know if I need or not, and so on.
   "rpm -e `rpm -qa|grep kde`" seemed to do the trick (although I fudged
upgrading qt to 2.4.4). Now I have a CLEAN 2.1 system.

Quote:> 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.

   I tried using the mdk 7.2 rpms - they complained about libmng and
libmcos, IIRC.

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.

If you maintain systems that run for years, upgrading as you go, you soon
find that this isn't so irrational. Try "upgrading" from WIn95 to 98, or
QNX4.21 to 4.25 without having a mess on your disk when you're done.

If you're following the development system (eg CVS) it can be OK. But I was
under the impression that KDE was NOT a "development system" - that it was
to be used by "normal users". I'm getthing the impression that this is not
the case. Too bad....

Lloyd Sumpter