anoncvs 1.8 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. * Anonymous CVS access
  2. Anonymous access to the Mono is available currently from three
  3. servers (anoncvs-spain-1.go-mono.com,
  4. anoncvs-spain-2.go-mono.com and anoncvs-us-1.go-mono.com).
  5. You can also use `anoncvs.go-mono.com', and that will pick a
  6. server automatically for you.
  7. Sources are currently being updated every hour.
  8. ** Checking out the sources
  9. To check out the sources for the first time from the
  10. repository, use this command:
  11. <pre>
  12. export CVSROOT=:pserver:[email protected]:/mono
  13. cvs login
  14. cvs -z3 co mcs mono gtk-sharp
  15. </pre>
  16. That will get you the compiler and class libraries (mcs), the
  17. interpreter and JITer (mono) and the Gtk# bindings.
  18. The server is located in Spain.
  19. ** Updating the sources
  20. To update your sources every day, you use this command:
  21. <pre>
  22. export CVSROOT=:pserver:[email protected]:/mono
  23. cvs -z3 update -dP mcs mono gtk-sharp
  24. </pre>
  25. ** Thanks
  26. Thanks to <a href="http://www.hispalinux.es">HispaLinux</a>
  27. for providing this Anon CVS server. The server is located in
  28. Spain.
  29. Special thanks to Jesus Climent, Rodrigo Moya, Juantomás
  30. García and Ismael Olea for making this happen.
  31. <a name="#mirror">
  32. ** Becoming an AnonCVS mirror
  33. To become an AnonCVS mirror, you currently need about 20
  34. megabytes of free disk space and bandwidth that you do not
  35. mind sharing (you probably want enough to spare).
  36. I need to be able to rsync to your machine from the main CVS
  37. server. The preferred method to rsync is to setup ssh in your
  38. machine.
  39. The requirements are:
  40. <ul>
  41. * An account where we can ssh into.
  42. * rsync.
  43. * AnonCVS setup with the same paths as the rest of the
  44. servers.
  45. * Currently, about 40 megabytes of disk space, but this
  46. will likely grow as the project evolves.
  47. * A sysadmin contact e-mail address.
  48. </ul>