For those of us that like to stay on the "bleeding edge" there's an easy way to keep a local copy of the KDE sources up-to-date - anonymous SVN.
Please note that several Linux distributions now already provide KDE SVN packages, so building Qt and KDE from source may well not be necessary for you at all! See Getting_Started/Distribution_Packages for instructions and information.
First, install the subversion (svn) binary if it isn't already on your computer. Your operating system should have a package for it. Alternatively you can download and compile it yourself via the svn project download page. Please read the KDE Subversion tutorial if you are interested in how to use Subversion.
/trunk/ is where the Qt4-based KDE 4 is being developed. The following is the minimal set of modules you will need to check out to build KDE and KDE software:
svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdelibs svn co svn://anonsvn.kde.org/home/kde/trunk/KDE/kdebase
|Only use "svn co" for the initial checkout, you will update your local sources afterwards by using "svn up modulename" or "svn update modulename".|
|If your firewall doesn't allow access to arbitrary ports, substitute svn://anonsvn.kde.org/ with svn://websvn.kde.org:443/ above.|
qt-copy is a copy of the latest stable Qt release which works with KDE, put into SVN for convenience. It also contains patches by KDE developers that haven't found their way to Qt yet. They are recommended for those working with KDE from trunk. You can obtain qt-copy by doing:
If you wish to have a complete copy of the KDE distribution, you can simply check out the entire source tree with one command:
|It is smarter to first use The KDE Source Repository Web Viewer. Use it to choose which modules to download. This way KDE will be quicker to install and try out.|
If you want additional software packages you can check out the following modules within trunk/ as well:
koffice extragear playground kdereview
So, for example, if you want to check out koffice trunk, you can use
If you are checking out modules from trunk/ you may be able to save time by using snapshots. Using Subversion trunk snapshots is described at the Subversion snapshots tutorial page.
If you want to track KDE 3 rather than the bleeding edge, you may retrieve the KDE 3.5 sources using:
svn co svn://anonsvn.kde.org/home/kde/branches/arts/1.5/arts svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/
And if you want the matching qt-copy:
KDE modules are also tagged at each release so that it is possible to get a specific release of KDE. Most KDE modules have a tag name in the format tags/KDE/X.Y.Z (where X, Y and Z represent the exact version). The arts module (only needed for KDE 2 and KDE 3) has a different format of tag name, tags/arts/X.Y.Z. For instance to get kdelibs as it was shipped in KDE 3.5.0, do:
If you then want to update this checkout to KDE 3.5.5, use this command:
|If you used a /branch/ or /trunk/ path, then there is no need to switch, just run svn update.|
|WebSVN is a convenient way to check for a tag name.|
If you are looking for translations and other localizations, check out the appropriate language from the l10n module.
|The l10n module is extremely large. Be sure you have lots of time and disk space on hand before checking out the entire l10n module. Most people only check out specific language subdirectories rather than the entire l10n module.|
svn switch --relocate svn://anonsvn.kde.org/ svn://kde.mneisen.org/
If you're interested in setting up a svn mirror, please contact Dirk Mueller.