If you’re a developer, version control software allows you to keep track of changes to your code. This is essential on projects where you’re working as part of a team, letting you track changes as they happen. While services like GIT are popular, especially for open-source software, alternatives like Subversion (SVN) offer more control.
Various SVN clients exist, but for Mac users, a popular option is SvnX. We first touched upon this simple, free and open-source Mac SVN client over a decade ago, with plenty of new features and changes to dive into since then. If you want to use SvnX, here’s everything you need to know to get started.
It's not Mac OS X native, but you can give Eclipse's SVN client a try. It works on Mac OS X, and it's pretty good. Supercard software for mac.
Other types of version control, like GIT, rely on a decentralized approach to version control. Each worker gets a copy of the code, they work on that code, and the changes are then patched (committed) onto the larger codebase.
Apache Subversion works differently. Rather than a decentralized approach, Subversion is centralized. There’s only a single, central code repository, with each developer working on their own parts to it. Each revision to the code is tracked, with the ability to revert to past versions made easy.
This offers administrators more control, more security, and can be an easier system to begin using. If the centralized approach is for you, then installing SvnX is your first step to using Subversion on Mac. This client adds a GUI interface to the Subversion terminal app.
Previous versions of SvnX required a manual install of Subversion on macOS before the client would work. Thankfully, macOS now includes a recent version of Subversion, so this is no longer necessary.
To install and run the most up-to-date version of SvnX, you’ll need to install the Homebrew package manager for macOS. Other available versions of SvnX, including those provided on the “official” but long-since abandoned SvnX website, simply won’t work on recent macOS installations because of its older 32-bit status.
After its first launch, macOS will allow SvnX to run without any further security issues.
When you first launch SvnX, you’ll be presented with a fairly basic screen. Listed on the left are two categories called Working Copies and Repositories.
Repositories are the central SVN servers you connect to. An SVN repository holds all the files for your project. When you update a file, a new revision tag is added to it, allowing you to distinguish between older and newer copies of your repository files.
Working copies are where local copies of repository files are saved. This allows you to make changes to your files locally before you commit them to the repository. Files are usually separated into different focus areas like trunk (for stable copies), branch (for files under active development) and tag (for copies of the main repo).
Each new revision you make will be listed in the Repository window for your SVN server. You can make new working copies on older revisions to “fork” your code and revert back to an older version, should you need to.
If you’re not using a version control system, every change you make to your code is final. You can’t move backward, and you can’t undo the changes you make further down the line. Using SvnX on Mac helps to deal with this problem, offering a simple and effective way to keep track of code changes.
SvnX is a little outdated, though, so feel free to use an alternative like Versions if it isn’t the right Mac SVN client for you. Of course, you can’t run before you can walk, so if you want to learn how to code, there are a number of services and apps out there to help you.