On Mon, 24 Sep 2001 09:14:43 -0500
[EMAIL PROTECTED] wrote:
| I'd like to upgrade my kde from 2.1.2 to 2.2.1 on my eD2.4. Since there
| aren't any rpms, compiling is the way to go. What precautions should I
| take to reduce the chance of the compilation messing my system up? Should
| I first remove kde 2.1.1 completely or can I have both on my system at the
| same time like kde 1.1.2 and kde 2.1.2? TIA
Caldera have mixed kde and kde2. Don't know why. When I compile from source,
I use the --prefix=/opt/kdex.y.z option for all packages. Then when I do
an install, all parts are placed here. You cannot rename this directory as
the kde install uses this name in lots of config files. So, you need to make
a symbolic link. What I do is:
1. Rename the Caldera supplied /opt/kde2 directory to something more like
the real version it is. Then make a symlink from that that points to
the original name. So, if the original directory was called /opt/kde2,
and it contains kde2.1.2, I would do this:
cd /opt
mv kde2 kde2.1.2
ln -s kde2.1.2 kde2
At this point, all is the same. It is just that the kde2 that is already
installed is 'out of harm's way' - if you also follow the next step.
2. Compile KDE2.2.1, using --prefix=/opt/kde2.2.1 for EVERY part you
compile. You can install without fear or hurting the currently installed
version. You will now have two directories, one called /opt/kde2.1.2 and
the other called /opt/kde2.2.1. And you will have kde2 pointing to kde2.1.2.
This procedure also lets you install the new KDE libraries so you can
work through the compile procedure without distrubing the current install.
Nothing in your existing install is altered.
3. When you want to switch to kde2.2.1, do this:
cd /opt
rm kde2 # !!! NOT 'rm -rf'.
ln -s kde2.2.1 kde2
ldconfig
This last step updates the system's ideas about libraries. You must run it
each time you switch between versions of KDE. It saves headaches.
As a test, then do this:
cd /opt/kde2/bin # This is the new stuff
ldd kdm
This should list all the libraries without any complaint. If there is a
complaint then somethign went wrong. Re-point kde2 to kde2.1.2 and solve
the problem.
4. I have noticed that kde2.2 and kde2.2.1 when installed from scratch
mess up the /opt/kde2/share/config/kdm/*rc file. In the list of
possible sessions, the installed file will contain ';' as the separator.
It should be set to ','. If you get a funny list of session types, this is
the reason. There is a similiar problem with the user list.
5. Press ALT-CTRL-BACKSPACE to try the new KDE.
If there is a problem, re-point /opt/kde2 back to /opt/kde2.1.2 until
it is solved. This works because kde2.1.2 is the unchanged original.
6. If you want to remove the kde2.1.2 RPMs, be sure that /opt/kde2 is the
original thing - not a symlink - when you do this. Otherwise the
wrong thing will be removed. You have been warned.
As an aside, the kernel modules are installed into directories
that keep different versions separate and available. Too bad KDE
don't adopt a similiar standard. Maybe more people would test KDE
if the various installs were by design separate. I know that you can
accomplist alot with the KDEDIR environment variable. However, as
paths are placed in config files when kde is installed, this may
lead to unexpected problems. The config files I expect KDE to use
are always in a directory with the original name I used when I
compiled/installed the packages. The link to /opt/kde2 is just to
help all those other packages that use /opt/kde2 instead. You see,
KDE does it both ways. JMTCW.
--
=====================================================================
Roger Oberholtzer E-mail: [EMAIL PROTECTED]
OPQ Systems AB WWW: http://www.opq.se
Erik Dahlbergsgatan 41-43 Phone: Int + 46 8 314223
115 32 Stockholm Mobile: Int + 46 733 621657
Sweden Fax: Int + 46 8 302602
_______________________________________________
http://linux.nf -- [EMAIL PROTECTED]
Archives, Subscribe, Unsubscribe, Digest, Etc
->http://linux.nf/mailman/listinfo/linux-users
