Building KDE from svn: using kdesvn-build
There are some things you have to be aware of when compiling KDE from svn with kdesvn-build. There has been some problems that I encountered when compiling kde, but I don’t clearly remember them, so I will suffice to the solution for now:
To use the current strigi library (the one you manually compiled with kdesupport), do this in the terminal:
$ export STRIGI_HOME=/home/$USER/kde/
remember that you have to do it after you have compiled kdesupport.
When building kdebase, make sure you remove soprano-devel. kdebase will mistakenly use the old soprano-devel rather than the one compiled with kdesupport.
Building KDE from svn: dependencies
So here is the list of dependencies I promised in the previous post:
OpenSUSE
alsa-devel
automoc4
avahi-devel
boost-devel
cmake
patch --> qt-copy
cups-devel
giflib-devel
kde4-filesystem
libQtWebKit-devel
libakonadiprotocolinternals-devel
libgpgme-devel
libqimageblitz-devel
libqt4-devel
libsmbclient-devel
libsoprano-devel
libtiff-devel
libxslt-devel
phonon-devel
shared-mime-info
strigi-devel
xine-devel
svn
make
libbz2-devel
hal-devel
avahi-compat-mDNSResponder-devel
mysql-devel
libjasper-devel
libical-devel
Yes, I compiled (am compiling right now, kdebase and it’s 94%) kde on OpenSUSE just for fun! I’ll play with OpenSUSE a little bit until F10 comes out, and then I’ll be back to my beloved Fedora!! 
Note that this list is for OpenSuse, BUT, the deps are the same for almost every other distro. Therefore, with a little bit changing the names according to your distros package naming conventions, you can get the same stuff. For example, in Fedora, libsoprano-devel would be soprano-devel and libQtWebKit-devel should be something like QtWebKit-devel.
