Version: 3.0.90 (using KDE 3.2.2, SuSE) Compiler: gcc version 3.3.1 (SuSE Linux) OS: Linux (i686) release 2.4.21-215-default It can be difficult to always rely on the CVS builds of KDevelop. I prefer to use the latest CVS when it's functional, and I hope my newly acquired C++ skills will enable me to constribute more directly to the project soon. Nonetheless, sometimes I need an alternative to the latest CVS. The way Gideon worked seems like a reasonable model. That is, having a separate set of configuration files from those used by the KDevelop release. That way, I can use the latest CVS without impacting the KDevelop SuSE provides for their distribution. They usually do a better job of integrating things into the reast of the environment than I can do working in user space. If it's just for my sake, please don't expend the effort. If other's believe the Gideon approach is beneficial, then it might be worthwhile.
There is another option which may be an acceptable alternative to the Gideon II I suggested. I can build and install (or install SuSE's RPMs?) and ssh -X otheruser@localhost -f '/path/to/kdevelop/startup/script.sh' (or '/usr/X11/xterm').
Yes, two alternatives: - We change a lot o code and create kdevelop_be (KDevelop bleeding edge) just like Quanta did. And Please do not mention the Gideon name never ever again. - You create a new user (I use be) and add this to you .bashrc export KDE_BE_DIR=/mnt/home/be/kde3 export KDEDIRS=$KDE_BE_DIR:/opt/kde3 export PATH=$KDE_BE_DIR/bin:$PATH export LD_LIBRARY_PATH=$KDE_BE_DIR/lib:$LD_LIBRARY_PATH Then make a cron job of the be user build and install the latest KDevelop every nigth (--prefix = /mnt/home/be/kde3) while you sleep using kdecvs-build or kdesdk/scripts/kde-build. I use and prefer the second option.