svn HowTo

If you look for a mini SVN tutorial and some very useful SVN links, please see this page.

svn tree

https://websvn.kde.org/ is available anonymously for having a brief look how SVN looks like
CVS users currently using ssh access, should use protocol svn+ssh,
CVS users currently using password access, should use protocol https in the following.

Checking out KDE 3.5

KDE 3.5 is in branches using the autotools while trunk is KDE 4.0 using unsermake.
If you want to check out KDE 3.5, you need first qt-copy 3.3 in branches/qt/3.3/, arts version 1.5 in branches/arts/1.5/arts and the other KDE modules in branches/KDE/3.5.
You also need kdesupport for taglib and akode if you want full multimedia support. kdesupport needs to be built before arts in that case.

Here are the correct paths:

svn co <protocol>://<username>@svn.kde.org/home/kde/branches/qt/3.3/qt-copy
svn co <protocol>://<username>@svn.kde.org/home/kde/trunk/kdesupport 
svn co <protocol>://<username>@svn.kde.org/home/kde/branches/arts/1.5/arts
svn co <protocol>://<username>@svn.kde.org/home/kde/branches/KDE/3.5/<module>

If you use https, you have to acknowledge the certificate before the checkout happens, but it's pretty straightforward.

svn diff, update, commit - they all work like cvs did. Of course you will find differences in the way it works compared to cvs, but I hope you will feel comfortable when you try it.

---

Anne-Marie Mahfouf
Last update: 2008-01-11