|This article is available in: English Castellano ChineseGB Deutsch Francais Italiano Nederlands Portugues Russian Turkce|
by Lorne Bailey
About the author:
Lorne lives in Chicago and works as a computer consultant specializing in getting data in and out of Oracle databases. Since making the switch to programming exclusively in a *nix environment, Lorne has completely avoided 'DLL Hell'. He is currently working on his Master's Degree in Computer Science.
KDE released their latest code as version 3 recently. This
article will give you an idea what it would be like to try it
for yourself. Though the article uses SuSE 7.3, but binaries
should be available for any major distribution.
The great thing about KDE3 is that you can test it out and still use KDE2 if you want to. If you're still using KDE1, you might want to upgrade your distro right away!
The problem for the KDE1 crowd is that the version of KDE3 I got in the rpm's uses the ~/.kde directory, so it can conflict with KDE1. You can get around that, too, if you work at it. KDE starts in the directory defined in the environment variable 'KDEHOME', so if you set that before starting KDE you should be set.
You can download the files for your distro from the KDE recommended mirror nearest to you:
What keeps KDE3 from interfering with previous versions? The programs and libraries go into their own directories so nothing gets destroyed when you install. Not like some OS's that put everything into some crazy 'registry' that no one really understands and that makes your machine useless when it gets corrupted by, for example, recompiling your code. That's a real problem when you develop software for a living and recompile constantly. On SuSE the KDE3 libraries go into /opt/kde3 and qt3 goes into /usr/lib/qt3. You should double check that there is no conflict by doing a 'rpm -qpl <package-name.rpm>' and look at the list of files the package contains. Also, rpm should give you a warning before you install anything.
You can install using rpm's pretty easily. I put all the rpm files I wanted to install in a separate directory and typed 'rpm --install *.rpm'. If it complains about dependencies, install the needed packages and try again. I did get one error about a file conflicting between KDE2 and KDE3. When I looked into the differences, it was two characters in one line of a script. I didn't think that it was a big deal, so I used 'rpm --install --force *.rpm' and haven't had a single problem.
Then you make one change to the kdm login manager. You go to KDE Control Center->System->Login Manager and add a session called kde3. This will call the /usr/X11R6/bin/kde3 that is a link to the KDE script that sets everything up so KDE3 runs correctly. KDE will ask you if you want to import your settings from KDE2. I did, and a couple of times the import of KMenu did not work correctly. Not a major issue, but it was inconvenient. I would recommend not using your old settings and taking the default setup instead. You can change it in 'kmenuedit' later if you like.
That should do it.
The really safest way is to wait for your distribution to put a tested upgrade onto a CD and go through their process. Let's face it, trying out new things isn't for everyone and just because I haven't had any problems doesn't mean you won't. I see the actual risks as very small. I upgraded 3 different machines so far and I wouldn't incur the wrath of those people if I thought KDE3 would ruin their machine. Having said that, as mentioned above you might have to force install over a script conflict. If this makes you nervous, you can back those files up and restore them if you have problems. Trying the upgrade does involve some basic knowledge of the system that could be intimidating. Not everyone likes to play around with new software since they just want to get things done.
|Startup from console||7||12||16||18|
|Startup from kdm||3||10||10||12|
|X - Didn't work for me because I broke it. * - Not Applicable.|
For Gnome I used Evolution as the Email client. It has a lot of functionality so I expect it to start slowly. Also, since I have upgraded my mozilla, Galleon doesn't work for me.
I am willing to wait that extra second when I'm starting an application because it's easy to use KDE the way I want to use it. This is where your personal preferences and needs kick in. I like Konsole more than I like eterm. Since I start a few applications and then use them for hours, startup time doesn't make any difference to me.
Webpages maintained by the LinuxFocus Editor team
© Lorne Bailey, FDL
Click here to report a fault or send a comment to LinuxFocus
2002-04-30, generated by lfparser version 2.28