| 123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657 | <!--#include file="header.html" --><h3>Anonymous CVS</h3>We allow anonymous (read-only) CVS access to everyone.  The first command youneed to run for anonymous CVS access is:<pre>cvs -d:pserver:anonymous@uclibc.org:/var/cvs login</pre><p>CVS will prompt you for a password. Just press the Enter key (there is nopassword for anonymous access).  This step only needs to be done once, the firsttime you attempt to access CVS.<p>Once the login is complete, you can then check the list of availableCVS modules by running the following command (all on one line):<pre>cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -c </pre><p>If you wish, you can then check out a local copy of any of the available modules.  The following is an example of how to grab a copy of uClibc:<pre>    cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc</pre>This will create a directory called <b>uClibc</b> in the current directory.  This directory will contain the latest and greatest sourcecode for uClibc.<p>If you are not already familiar with using CVS, I recommend you visitthis quick <a href="/cvs_howto.html">Introduction to CVS</a>.<p>I usually create a ~/.cvsrc file with the following things in it, and Irecommend you should use the same:<pre>    -z3    update -dP    rdiff -u    diff -ubBwpN    checkout -P</pre><p> Once you've checked out a copy of the source tree, you can update yoursource tree at any time so it is in sync with the latest and greatest byrunning the command:<pre>cvs update</pre>Because you've only been granted anonymous access to the tree, you won't beable to commit any changes. Changes can be submitted for inclusion by postingthem to the appropriate mailing list.  For those that are actively contributing<a href="cvs_write.html">CVS write access</a> can be made available.<!--#include file="footer.html" -->
 |