Subversion migration
(Git) |
(CVS to git has happened!) |
||
| (One intermediate revision by one user not shown) | |||
| Line 1: | Line 1: | ||
| − | This page will | + | This page will outlined plans for migrating Biopython from [[CVS]] to [[SVN|Subversion (SVN)]], although in the end we [[GitMigration|switched straight to Git]] instead. |
== Biopython Users == | == Biopython Users == | ||
Latest revision as of 12:21, 24 September 2009
This page will outlined plans for migrating Biopython from CVS to Subversion (SVN), although in the end we switched straight to Git instead.
Contents |
Biopython Users
Content for users to be created.
Installing Subversion
Microsoft Windows
Download and install either TortoiseSVN or RapidSVN. There is also a binary available for a command line based Subversion client; see the Subversion website.
Mac OS X
Download and install Subversion via Fink or the binary package.
Linux
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 located within /usr/bin/.
user@compy$ which svn
user@compy$
On the other hand, in the above example, which 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
Biopython Developers
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.
Biopython Migration Strategy
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.
