[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    developer.kde.org/source
From:       Dirk Mueller <mueller () kde ! org>
Date:       2005-07-31 19:23:08
Message-ID: 1122837788.760558.21148.nullmailer () svn ! kde ! org
[Download RAW message or body]

SVN commit 441727 by mueller:

updates


 M  +23 -6     anonsvn.html  


--- trunk/developer.kde.org/source/anonsvn.html #441726:441727
@@ -16,7 +16,8 @@
 Using anonymous SVN is simple:
 <ol>
     <li>Install the SVN binary. Your distribution should have one.
-        Alternatively you can download and compile it yourself via <a \
href="http://subversion.tigris.org/project_packages.html">SVN download page</a>. +    \
Alternatively you can download and compile it yourself via +        <a \
href="http://subversion.tigris.org/project_packages.html">SVN download page</a>.  \
</li>  <li>The following is a minimal set of modules you need:
     <br />
@@ -30,25 +31,41 @@
     </li>
     <li>The various KDE modules have tags so it is possible to get a specifc release \
of KDE.  Most KDE modules, apart from arts, have a tag name in the format \
tags/KDE/X.Y.Z (where X, Y and Z represent the exact version). The arts module has a \
different format of tag name, tags/arts/X.Y.Z. <a \
href="http://websvn.kde.org/tags/">WebSVN</a> is a convenient way to check for a tag \
                name. For instance to get KDE 3.4's kdelibs, use
-    <code>svn co svn://anonsvn.kde.org/home/kde/tags/KDE/3.4.0/kdelibs/</code>
+    <code>svn co svn://anonsvn.kde.org/home/kde/tags/KDE/3.4.0/kdelibs/</code>.<br>
+     If you then want to update to KDE 3.4.1, use this command: 
+     <code>svn switch svn://anonsvn.kde.org/home/kde/tags/KDE/3.4.1/kdelibs</code>.
+     If you used a <code>/branch/</code> or <code>/trunk/</code> path, then there is
+     no need to switch, just run <code>svn update</code>.
     </li>
+    <li><b>NOTE:</b>trunk is moving into the direction of KDE 4, which means it is \
based +     on Qt 4 and generally very few things work or compile at all. You're most \
likely interested +     in staying on the stable branch, which is KDE 3.5 currently. \
To check out KDE 3.5, use: +     <code>
+       svn co svn://anonsvn.kde.org/home/kde/branches/arts/1.5/arts<br />
+       svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdelibs<br />
+       svn co svn://anonsvn.kde.org/home/kde/branches/KDE/3.5/kdebase<br />
+       ...
+      </code>
     <li>
-    If you want to have a full copy of the KDE distribution (including whole \
kde-i18n!), you want to check out +    If you want to have a full copy of the KDE \
distribution, you want to check out  <br /><code>
       svn co svn://anonsvn.kde.org/home/kde/trunk/KDE
     </code>
     <br />
     If you want additional sources, you can check out the following modules:
-    <br /><ccode>
-      qt-copy<br />
-      kmusic<br />
+    <br /><code>
       koffice<br />
       extragear<br />
       kdenonbeta<br />
       playground<br />
       kdereview<br />
     </code><br />
+      if you're looking for the internationalisation, check out the \
<code>l10n</code> module (Warning: HUGE!).  </li>
+   <li>
+     Please read the <a \
href="http://developer.kde.org/documentation/tutorials/subversion/">KDE Subversion \
tutorial</a> +     if you're more interested in how to use Subversion.
+   </li>
    <li>qt-copy is a copy of the latest stable <a \
href="http://www.trolltech.com">Qt</a> release which works with KDE, put into SVN for \
convenience. It contains additional patches that fix bugs or add enhancement KDE  can \
                make optionally use of.
        Qt and KDE need to know where Qt is compiled, so do an <code>export \
QTDIR=/your/dir/to/qt-copy</code>


[prev in list] [next in list] [prev in thread] [next in thread]