Well then, lets solve that “problem” shall we.
Basicly there are four ways to get SubVersion going on your Mac.
- Build it yourself…
- Get something pre built, sanctioned by subversion themselves (do scroll down a bit to the second option under Mac OS X)
Lets see, for those wanting to do some hacking, choose option 1. If Fink sounds familiar, then go for a Fink install by choosing option 2, do choose the svn-ssl package, else you wont get encryption support. Those who are more familiar with DarwinPorts, go for option 3. And finaly for those that just want to get going with SubVersion (aka svn), go for option 4.
Options 1, 2 and three are pretty simple for those who’ve done “that” before. Option 4 should be a blast too, just click a bit, wait a bit and you are done.
After having installed SubVersion, make sure its working by opening a Terminal window. (Take a peak in “Application\Utilities” to find it.) And then type
svn<enter>. You should see
svn help apear on your screen.
Now we’ve got SubVersion. Feels great doesn’t it? But now, what to do with this über tool.
Also when in Terminal, check the man pages for the various tools and try adding the word
help as a parameter.
But wait, I’m a Mac user, and you’re a Mac user (because you’ve gotten this far). Now we want something squishy. We want pretty windows and buttons to click on. Well there are several options to choose. But I like SVNX the most.
Do note that practically all tools need the commandline tools installed in advance. Also you might have your svn executables installed in a non default location, so any decent SVN tool shoul provide a configuration option so you can specify where your executables are on your system. (Try a
which svn in Terminal to find out where they are.
If anybody prefers other graphical tooling, please feel free to post your opinion as a comment.
And one word of caution when using subversion on a mac. The system harddrive on your mac and most other hard drives are probably formatted “case preserving, case insensitive”. This can get nasty when using SubVersion from a Mac and other non-Mac systems. You could check in two files called “myFile” and “MyFile” on a non-mac system. (Notice the different casing of the letter “M”.) And then try to check those files out on a mac. SVN will most likely start complaining, because although a mac preserves the case in the file name, it doesn’t care which letter are small case or capital. To a mac it usually is all the same, so your pretty mac just starts overwriting. So steer clear of differentiating files by case alone. It’s a bad practice anyway, eventhough those Perl hackers seem to like it sometimes, it’s better not to do it.
Last bit of info, when updating your SubVersion binaries, allways, and I really mean ALLWAYS, check the release notes when you are hosting your own repository. Up untill now it’s been easy going to update SubVersion, but sometimes little things are important when updating.
Have fun with SubVersion… 🙂