going braindead, installing kde3.2
 

i know i'm forgetting something simple. im running mandrake 9.2 (updated to 2.6 kernel) and just installed kde3.2 using Konstruct. all that worked, its installed etc. but post-installation the Konstruct readme says to add the new kde paths to $PATH, $QTDIR, etc etc, couple others. i for the life of me cannot remember how to do this at startup so that KDM will log me into 3.2 instead of 3.1.3. naturally if i just do export path=~/kde3.2:$path that doesnt stick.

i know i'm gonna hate myself when i hear that answer to this. =)

I am having the same exact problem. ( I orginally messed my kde 3.1.x ( dont know ) up so bad that I cant even get into it so I decided to just get kde 3.2 I used konstruct and it did all its stuff, and now when I try to export none of the stuff saves. My kde 3.2 doesnt load at all. I did all the exports and then they dont save when I log out. I'm a linux nub btw

bumped for great justice..

tried adding export lines to /etc/rc.d/sysinit thinking that might do the trick, still no dice.

The PATH variable should be set in /etc/profile if it's a global thing, otherwise it should be set in ~/.bash_profile. You will want this to be global, so edit /etc/profile. The old version should already be set there.
The best thing to do however is have everything relative to a symlink, so you install kde in /opt/kde-version, and symlink it to /opt/kde. Everything refers to /opt/kde, so when you install a new version, you just change the symlink. Even if that's not how you've done it, you can just move things around like so:
mv /opt/kde-oldversion
[for old version] ln -s /opt/kde-oldversion /opt/kde
[for new version] ln -s /opt/kde-newversion /opt/kde
Hope this helps
Guy

tried both of those ideas, still no dice.

see, what i did is, i installed kde3.2 to /home/<user>/kde3.2 so that it wouldnt interfere at all with my kde3.1.3 install. i'd like to add another choice to the Display Manager dropdown at login so that i have kde3.2 in there (alongside kde, gnome, icewm, etc etc). any ideas how to go about doin that one?

HI There,

Might be of some help I have had custom installs of KDE 3.2 CVS working in RED HAT 9.0 and Fedora Core 1 as well as SuSE 9.0. First thing is KDE 3.2 has just been released you might want to go along and grap the rpms for your distro if all you wanted was KDE 3.2, at least for SuSE 9 this would sort your login out to log into the correct KDE session.

Otherwise the previsous information on setting your .bashrc file out is what you need to do the instructions are lying around somewhere on the KDE web site. At uni at the moment so can't take a look at my file but you need to set

QTPATH:
KDEPATH:

You will also need to add the links to you libarys such as KDEPATH:/lib in LD_CONFIG_PATH. I will take a look at my file and then put it up on here so that you can see what I did it might work for you.

As for chossing which kde you want to boot, not too sure about that but the informtion so far looks about write. I am sure a fast google around and you will find the answer to that

Oh just found it on the kde website

QTDIR=/usr/local/qt-stable
KDEDIR=/usr/local/kde-stable
KDEHOME=/home/example/.kde-stable
PATH=$PATH:$QTDIR/bin:$KDEDIR/bin
LD_LIBRARY_PATH=$QTDIR/lib:$KDEDIR/lib
export QTDIR KDEDIR PATH LD_LIBRARY_PATH

set all of these in something like .bashrc (Thats Red hat and Fedora) or .profile or .login you get the idea.

Just as a note, I had problems with startkde not working write so i had to use the version that i compiled, it should be in /kdedir/bin.

Hope that makes some sense if not post back and I will try to make more sense

David