cvs_anon.html 1.8 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657
  1. <!--#include file="header.html" -->
  2. <h3>Anonymous CVS</h3>
  3. We allow anonymous (read-only) CVS access to everyone. The first command you
  4. need to run for anonymous CVS access is:
  5. <pre>
  6. cvs -d:pserver:anonymous@uclibc.org:/var/cvs login</pre>
  7. <p>
  8. CVS will prompt you for a password. Just press the Enter key (there is no
  9. password for anonymous access). This step only needs to be done once, the first
  10. time you attempt to access CVS.
  11. <p>
  12. Once the login is complete, you can then check the list of available
  13. CVS modules by running the following command (all on one line):
  14. <pre>
  15. cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -c </pre>
  16. <p>
  17. If you wish, you can then check out a local copy of any of the
  18. available modules. The following is an example of how to grab
  19. a copy of uClibc:
  20. <pre>
  21. cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc</pre>
  22. This will create a directory called <b>uClibc</b> in the current
  23. directory. This directory will contain the latest and greatest source
  24. code for uClibc.
  25. <p>
  26. If you are not already familiar with using CVS, I recommend you visit
  27. this quick <a href="/cvs_howto.html">Introduction to CVS</a>.
  28. <p>
  29. I usually create a ~/.cvsrc file with the following things in it, and I
  30. recommend you should use the same:
  31. <pre>
  32. -z3
  33. update -dP
  34. rdiff -u
  35. diff -ubBwpN
  36. checkout -P</pre>
  37. <p>
  38. Once you've checked out a copy of the source tree, you can update your
  39. source tree at any time so it is in sync with the latest and greatest by
  40. running the command:
  41. <pre>
  42. cvs update</pre>
  43. Because you've only been granted anonymous access to the tree, you won't be
  44. able to commit any changes. Changes can be submitted for inclusion by posting
  45. them to the appropriate mailing list. For those that are actively contributing
  46. <a href="cvs_write.html">CVS write access</a> can be made available.
  47. <!--#include file="footer.html" -->