Subversion on Mac OS X is a post by Jeffrey McManus of Platform Associates. Follow Jeffrey on Twitter.

Related posts:

1. A Rank Amateur Upgrades His Subversion Repository
2. All About Subversion
3. Dear Last.fm,

I’m an OK programmer, but I was born without that part of the brain that lets me do system administration tasks confidently. For people who don’t have hands-on experience with either programming or administration, or both, this probably sounds nutty: "C’mon, you’re a big computer guy, you can make them bow to your will, what is it about server administration that makes you soil yourself and cower in the corner like a little girl?" I’m not sure. I suspect it’s because the support and documentation characteristics for administrative tasks and programming tasks tend to be very different. I tend to learn by example, and most books on system administration bombard you with 100 pages of background information before they show you the first example of what you really want to do. I realize that there may be a good reason for this, but it doesn’t keep me from falling asleep by the time I get to page 4 of the manual.

Anyway. I’m trying to keep up with the latest build of Subversion as it approaches its 1.0 release. (Update: Subversion has shipped version 1.0 since this was originally written; I’ve updated this to reflect a minor change in the original upgrade procedure.)

When Subversion was in development, every so often they would need change the database schema. When that happens, you have to perform a dump of my repository, install the new version, and import the dump files. Not a huge deal to a system administrator with an iron constitution, but to me: yikes. So when I upgraded from version 0.35 of Subversion, I very carefully wrote everything I did down. I share my notes for your benefit, if you should happen to find yourself in the same situation I was in. (Nota bene, I’m running Subversion on Windows 2000 Server, so that’s what these instructions will apply to.) My upgrade went flawlessly, by the way, despite my angst, and the Subversion documentation on repository migration is quite excellent, actually.

Upgrading A Subversion Repository
1) Per http://svn.collab.net/repos/svn/trunk/CHANGES, first  use  ’svnadmin dump’  with  your existing version of Subversion.

    svnadmin dump D:\svn\test > D:\Program Files\Subversion\dumpfiles\test.dump

(Do this for any other repositories you have as well.)

2) Upgrade your Subversion binaries to the latest version:

  a) Stop Apache service (net stop apache2)
  b) Launch the installer (svn-1.0.0-setup.exe) or, if you use the non-installer zip distribution, copy the files manually to wherever your Subversion binaries live (on my machine, it’s "\Program Files\Subversion")
  c) Move contents of \Subversion\apache2\modules to \Apache2\modules (Update: In the 1.0 Subversion distribution, these files are now stored in \httpd)
  d) Rename repository root (d:\svn) to something else (like d:\_svn)
  e) Start Apache service (net stop apache2)
 
Question: Installer says "Replace any libdb40.dll with this package’s libdb42.dll". Not sure what to do here; I’ve got a libdb40.dll in d:\program files\subversion, but there’s a libdb42.dll in d:\program files\Subversion\bin. Am I supposed to blow away the libdb40.dll in the Subversion directory? It seems to be working OK now, so I’m going to assume the answer is actually "no".

3) Re-create your repositories using svnadmin create.

	mkdir d:\svn	svnadmin create D:\svn\test

(Do this for other repositories you have as well.)

4) Use  ’svnadmin load’  to  create  a  new  repository  from your dumpfile.                                                      

	svnadmin load D:\svn\test < "D:\Program Files\Subversion\dumpfiles\test.dump"

(Do this for any other repositories you may have as well.)

5) The Subversion installer says "Don’t forget to copy any custom configuration/hooks from the old to the new repository." I don’t have any of these filthy beasts so I’m done.

A Rank Amateur Upgrades His Subversion Repository is a post by Jeffrey McManus of Platform Associates. Follow Jeffrey on Twitter.

Related posts:

1. All About Subversion
2. Subversion on Mac OS X
3. Unintended Consequences of Software Upgrades

Here’s a really brief layman’s description of the Subversion version control system along with some links to resources about it. Since this most excellent tool is approaching its 1.0 release, you might want to check it out, if you’re into that kind of thing. I’m not as well-versed with Subversion as I’d like to be, so feel free to post a comment if I got anything wrong.

I’m really interested in the way people organize information and, in a more general sense, how technology can help people work more intelligently. Using technology to get more organized really pumps me up.

I’m really fascinated by version control systems. I think SourceSafe reeks, but that’s not news; everyone who uses SourceSafe thinks it reeks. I used a commercial product Perforce for a while and I liked that, but it’s kind of expensive ($750/seat) and a lot of purists don’t like it because it, like SourceSafe, uses locksexpects that you’ll use locks, although it apparently doesn’t require locks by default (see comments).

Locking version control systems force you to check out a file to edit it. Locking is good because it means that two people can’t muck with the same file at the same time, but it’s bad because two people can’t muck with the same file at the same time. And if I check out a file, go to lunch, and get hit by a bus, you are hosed, at least until you can track down a repository administrator to release my lock on the file.

The most prevalent version control system in the open source world today is a free product called CVS. A lot of people think it reeks too, but they continue to use it because it reeks less than all the other stuff out there. (Like other ancient protocols which also reek yet continue to exist as part of the DNA of the Internet — SMTP comes to mind — CVS seems to have persisted for so long because it has persisted for so long).

CVS doesn’t lock files by default. Instead, if you want to work on something, you just start working on it. If it should happen that I changed the file while you were working on it, either you or I can merge our changes to the file using software tools that are specifically tailored to that purpose. This enables projects to scale up to hundreds of developers without the need for a lot of centralized management — perfect for open-source projects.

Subversion is a version control system that attempts to take the goodness from CVS (such as an easily automated command-line interface and a lack of locking) and get rid of some of its long-standing shortcomings — such as the lack of ‘atomic commits’. The ability to do atomic commits means that if you make changes to more than one file, you can specify that all of the files you’re working on must be checked in as a single ("atomic") unit. In a world in which changes to multiple files often have critical interdependencies, this is a nifty feature. But there are other important benefits to using Subversion as well, such as efficient handling of binary files and an easy way to browse repositories with a Web browser (thanks to the fact that Subversion is built on top of the Apache Web server).

Subversion, like CVS, is also an open-source project. But unlike CVS, a lot of development resources are being devoted to it today. Subversion is currently close to a 1.0 release; its own team have been using it to store their own source code for many months now. They say that neither they nor anyone else have lost data with it.

I wrote this mainly to kick off a new category devoted to Subversion; I have a couple of projects I’m working on that I’d like to use it for. So I’m going to try to devote some time to learning it well.

The book Version Control with Subversion is the definitive book on Subversion. The pre-publication version is available free online today, but the book will supposedly find its way into print at some point (I think O’Reilly is going to publish it, and I understand that APress is working on their own Subversion book as well, which is great).

TortoiseSVN is a nifty GUI front-end for Subversion that provides deep integration into the Windows shell. If you ever wanted to right-click on a file and add it to a version control repository, TortoiseSVN is what you want. This is the tool that I use to do 99% of my daily interaction with Subversion.

There is a Visual Studio .NET add-in for Subversion called AnkhSVN.

Subway is a project to create an SCC provider for Subversion. SCC providers let you get to a source control system from development environments that supports Microsoft’s SourceSafe integration API (this means Visual Studio and Visual Basic, but also others such as Macromedia Dreamweaver). This looks like it will be a great choice if you have existing SourceSafe users that want a relatively seamless upgrade path, but it also looks like this tool is a work in progress; the first (and only) release was put out in April 2003, and the last update to the Subway Web site was in June 2003.

Subversion has its own client API for C/C++ that you can use to integrate Subversion repositories into your applications. Here is an article by Garrett Rooney on using the Subversion Client API. Here is part two of that article. The full Subversion API documentation is here.

Updated 28. Dec 2003 to reorganize and provide more details for Subversion utilities for Windows, in particular the indispensible TortoiseSVN and the unfortunate not-ready-for-prime-time-ishness of Subway.

All About Subversion is a post by Jeffrey McManus of Platform Associates. Follow Jeffrey on Twitter.

Related posts:

1. A Rank Amateur Upgrades His Subversion Repository
2. Subversion on Mac OS X
3. Installing the MySQL ADO.NET Connector into the Global Assembly Cache