I've been meaning to try to see if Subversion is a viable version control tool within a group of developers. I've been using it myself as an alternative to Visual Source Safe about a year ago after stumbling on it while trying to figure out why VSS was killing my projects.
This morning, I finally upgraded my SVN version to the latest release, 1.3, and tried to set up the HTTP access as well. I had never set up that piece before as no one actually wanted to dip their toes in with me, so there was no need to share access. After a lot of struggling with Apache 2.2, the latest release, I decided to give up on it. The current build of the Windows distribution of Subversion 1.3 is incompatible with Apache 2.2 due to the a change in the APR versions (Apache Portable Runtime) from .9 to 1.2. I was just too damned lazy to figure out how to rebuild the projects Maybe next time. So I had to settle for Apache 2.0...but all is well now (thanks Nader)!
I plan on putting together a simple workshop for this in the near future as it was terribly difficult to find anything up to date and end-to-end. Anyways, here are a few good reading points to get started with:
- How to setup a .Net Development Tree.
- A series of blog postings/articles on Subversion on Windows.
- Open source Subversion documentation.
- Subversion general usage (with pictures!).
- Why not VSS?