Aintravingr8

So your not familiar then with the Konstruct build process? I was under the assumption that Konstruct goes out and download's all the source or rpm's if you will and does a full build of KDE 3.1.4. Isn't that what they advertise? It seems as though all the packages require an additional package which would assume that an automated build would be a much more efficient method of deployment.

OK so I'm fairly new to this whole open-source Linux deal and recently aquired RedHat 9. Dual boots quite well with Windows XP so I was impressed in that aspect. What I want to do now is upgrade my default load of KDE to the newest version 3.1.4. I ran through the Konstruct routine via \konstuct\meta\kde\make install, all seems well. I made the necessary additions to the path statement to include: export QTDIR=~/kde3.1.4 export KDEDIRS=~/kde3.1.4 export LD_LIBRARY_PATH=~/kde3.1.4/lib export PATH=~/kde3.1.4/bin:$PATH Setting KDEHOME too, e.g. "export KDEHOME=~/.kdetest", will tell KDE to save your settings to this directory and leave default ~/.kde directory unaffected. On shadow password systems you have to set $(prefix)/bin/kcheckpass SUID root or SGID shadow - otherwise you will not be able to unlock a locked desktop. The complete KDE desktop is started with "startkde", most distributions start it if you set it to the WINDOWMANAGER variable in your shell initializations. Now my problem is when I STARTKDE, it reverts back to the older file manager/splashscreen and each application that I supposedly updated indicates the old version. I am able to browse the bin directory and load konqueror for instance but gives me an error "protocol not supported" upon startup. Also the options are all greyed out as well. Anyone have success installing this? Can you give me some insight on resolution. thanks,