Content for users to be created.
Some distributions come with the Subversion packages by default, or they
may have already been installed by your system administrator. Verify
whether you have Subversion installed using `which`
user@compy$ which svn /usr/bin/svn user@compy$
In the above example, Subversion is installed and its executable is
user@compy$ which svn user@compy$
On the other hand, in the above example,
svn returns nothing.
This indicates Subversion is not likely installed. You or your system
administrator will need to use the appropriate package manager to
download and install the packages for Subversion. For example, on
Ubuntu, users would execute the following:
user@compy$ sudo apt-get update && sudo apt-get install subversion
Existing developer accounts should all continue to work as before. When working with the main trunk, basic operations such as checking out code, diff, and committing changes are very similar to those under CVS.
Currently this is being discussed on the Biopython developers mailing list, where there is a general consensus that moving to a distributed version control system (DVCS) would be more worthwhile than simple moving from CVS to SVN. See the git migration page.