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

List:       kde-commits
Subject:    www/areas/pim/development
From:       Adriaan de Groot <groot () kde ! org>
Date:       2005-02-11 23:14:07
Message-ID: 20050211231407.A23F11D1F9 () office ! kde ! org
[Download RAW message or body]

CVS commit by adridg: 

Very brief guide


  M +43 -0     start.php   1.8


--- www/areas/pim/development/start.php  #1.7:1.8
@@ -94,4 +94,47 @@
 </p>
 
+<h2>The really short guide</h2>
+
+The three-step guide to getting KDE PIM HEAD checked out from (anonymous)
+CVS. This will let you build KDE PIM from source; there's an hour or
+two delay behind the main CVS server, so you won't get <i>the</i>
+latest and greatest, but it's close enough.
+(This three-step guide excepted from the
+quality team's <a href="http://quality.kde.org/develop/cvsguide/buildstep.php">step-by-step guide</a>.)
+
+<ol>
+<li>Create a file <tt>.cvsrc</tt> in your home directory containing
+the following:
+<div class="shellcode">
+cvs -q -z4
+diff -u3 -p
+update -dP
+checkout -P
+</div>
+</li>
+<li>Log in to CVS with the following commands:
+<div class="shellcode">
+export CVSROOT=:pserver:anonymous@anoncvs.kde.org:/home/kde
+cvs login
+</div>
+When prompted for a password, hit enter.
+</li>
+<li>Check out the KDE PIM sources with the following command
+(assuming it's still the same shell as you used to log in,
+otherwise enter that <tt>export</tt> command again):
+<div class="shellcode">
+cvs co kdepim
+</div>
+</li>
+</ol>
+
+There! That's all there is to it.
+You can <tt>cd</tt> into the directory <tt>kdepim/</tt>
+and start work. In future, when <i>in</i> that directory,
+enter the following command to stay up-to-date:
+
+<div class="shellcode">
+cvs update
+</div>
 
 <!-- END CONTENT -->


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