The Subversion sources are now under revision control in a
Subversion repository. The CVS
repository is obsolete (though you can still browse online
the old CVS
ChangeLog, or
the old CVS repository itself).
For the impatient: by pointing your web browser directly at
Subversion's repository, you can browse the latest source.
Because we use HTTP/WebDAV/DeltaV as our network protocol, we get very
basic 'web' functionality for free.
For real work: you need to "bootstrap" Subversion. That is,
use Subversion to check out a working copy of its latest source tree.
Download the latest tarball distribution from the Downloads
Page.
Build and install it according to the instructions in the
INSTALL
file in the top level of the distribution. You will end up with a
'svn' binary in the subversion/clients/cmdline/ directory (or
installed in /usr/local/bin/, if you ran 'make install'.)
Use it to check out the newest Subversion source:
$ svn co http://svn.collab.net/repos/svn/trunk subversion
That will get you a new working copy directory named
`subversion/', containing the latest, bleeding-edge source. (If
you're behind a proxy or have problems with the checkout, see the
proxy faq.)
(Some people have reported DNS lookup errors for `svn.collab.net'.
The IP address is 216.127.237.133, in case you should need it.)
-
cd subversion
svn status
svn update
etc, etc, etc...
Now you have a working copy. Most commands work like you
would expect. Many of them have bugs, or misconfigured defaults.
Many features are missing. Please make sure you're subscribed to
dev@subversion.tigris.org if you're going to run this.
Here's a hint: read the Subversion
Handbook, and in particular its SVN for CVS Users
appendix. It should help.
Generally, you should always rebuild and install Subversion
from your working copy (read the INSTALL and HACKING files). The
latest available tarball is still not as recent as an up-to-date
working copy.
Read the Warnings
and Inconveniences Page for information about some particularly
annoying bugs and their workarounds.
|