Free subversion software for mac

The goal of the Subversion project is to build a version control system that is a compelling replacement for CVS in the open source community. The software is released under an Apache/BSD-style open source license.

• Most current CVS features.
Subversion is meant to be a better CVS, so it has most of CVSs features. Generally, Subversions interface to a particular feature is similar to CVSs, except where theres a compelling reason to do otherwise.
• Directories, renames, and file meta-data are versioned.
Lack of these features is one of the most common complaints against CVS. Subversion versions not only file contents and file existence, but also directories, copies, and renames. It also allows arbitrary metadata (properties) to be versioned along with any file or directory, and provides a mechanism for versioning the `execute permission flag on files.
• Commits are truly atomic.
No part of a commit takes effect until the entire commit has succeeded. Revision numbers are per-commit, not per-file; log messages are attached to the revision, not stored redundantly as in CVS.

• Apache network server option, with WebDAV/DeltaV protocol.
Subversion can use the HTTP-based WebDAV/DeltaV protocol for network communications, and the Apache web server to provide repository-side network service. This gives Subversion an advantage over CVS in interoperability, and provides various key features for free: authentication, wire compression, and basic repository browsing.
• Standalone server option.
Subversion also offers a standalone server option using a custom protocol (not everyone wants to run Apache 2.x). The standalone server can run as an inetd service, or in daemon mode, and offers basic authentication and authorization. It may also be tunnelled over ssh.
• Branching and tagging are cheap (constant time) operations
There is no reason for these operations to be expensive, so they arent.
Branches and tags are both implemented in terms of an underlying copy operation. A copy takes up a small, constant amount of space. Any copy is a tag; and if you start committing on a copy, then its a branch as well. (This does away with CVSs branch-point tagging, by removing the distinction that made branch-point tags necessary in the first place.)

• Natively client/server, layered library design
Subversion is designed to be client/server from the beginning; thus avoiding some of the maintenance problems which have plagued CVS. The code is structured as a set of modules with well-defined interfaces, designed to be called by other applications.
• Client/server protocol sends diffs in both directions
The network protocol uses bandwidth efficiently by transmitting diffs in both directions whenever possible (CVS sends diffs from server to client, but not client to server).
• Costs are proportional to change size, not data size
In general, the time required for a Subversion operation is proportional to the size of the changes resulting from that operation, not to the absolute size of the project in which the changes are taking place. This is a property of the Subversion repository model.

• Choice of database or plain-file repository implementations
Repositories can be created with either an embedded database back-end (BerkeleyDB) or with normal flat-file back-end, which uses a custom format.
• Versioning of symbolic links
Unix users can place symbolic links under version control. The links are recreated in Unix working copies, but not in win32 working copies.
• Efficient handling of binary files
Subversion is equally efficient on binary as on text files, because it uses a binary diffing algorithm to transmit and store successive revisions.
• Parseable output
All output of the Subversion command-line client is carefully designed to be both human readable and automatically parseable; scriptability is a high priority.
• Localized messages
Subversion uses gettext() to display translated error, informational, and help messages, based on current locale settings.

Subversion support for Interface Builder and EOModeler extends EOModeler and Interface Builder (Mac OS X 10.2) so that .svn directories for nibs/eomodels under subversion are not trashed when documents are saved.
Subversion is meant to be a better CVS, so it has most of CVSs features.

iSubvert is an easy to use combined Subversion and SFTP Mac client aimed at web developers.
iSubvert will allow you to work with remote working copies - that is, you can perform SVN commands on a remote server.
Local working copies are also supported on Mac OS X provided the subversion client binaries are installed.

Main features:
- SFTP client - browse, manage, and edit files over SFTP
- SVN client - performs most subversion commands, anything missing is coming soon.

System requirements:
- Ability to connect to your server over SSH and SFTP
- Subversion client binaries installed on your server
- Mac OS X local working copies require installation of command-line subversion client binaries

Enhancements
Features:
- Reworked main window UI, more native looking on each platform.
- Updated keyboard shortcuts and improved keyboard-based navigation.
- SVN Export tool.
- Symlinks editable in Get Info window.
- Log message shown on historic diffs.
- More SVN tools work in the SFTP window (now fetches info about which files are in the repo).
- Create and Extract remote tar and zip archives.
- Max. Connections per Server preference.
- Various performance improvements.
Fixes:
- Cancelling auto update now works.
- Blame window fixes.
- Fixed filename display when showing historic diffs.
- Fixed duplicate file or folder when parent path contains a "." but basename doesnt.
- Error reporting when trying to create a file / directory that already exists.

SmartSVN Professional 6.0 is a highly efficient, high-quality platform-independent Subversion (SVN) client which will not let you down. Although it contains very powerful features, it is very easy to use, especially for users of SmartCVS who switched to Subversion.

SmartSVN is self-contained, no need to install seperate applications like Subversion command line client or file compare tools. SmartSVN is available in two versions, the commercial Professional version and the feature-reduced free Foundation version.

ReviewMonk is a code reviewing tool for Subversion built with Ruby on Rails. Its a webserver that runs on your machine and allows you to share all your local code changes with others before you check them in.
Main features:
- Allows other developers to see your local changes
- Allows users to see affected files (both versioned and not) and navigate your source tree
- URLs are shareable and easy to cut and paste to other users
- Works with Subversion
- Provides colorized diffs between revisions
- Provides syntax highlighting for Ruby, YAML, & XML
System requirements:
- ruby (1.8.4)
- ruby on rails (1.2.3)
- syntax (1.0.0)
- escape (0.0.1)
- mongrel (1.0.1) - optional
NOTE: ReviewMonk is released under the MIT license.

Envers project aims to enable easy versioning of persistent classes. All that you have to do is annotate your persistent class or some of its properties, that you want to version, with @Versioned. For each versioned entity, a table will be created, which will hold the history of changes made to the entity.
Similarly to Subversion, the library has a concept of revisions. Basically, one transaction commit is one revision (unless the transaction didnt modify any versioned entities).
As the revisions are global, having a revision number, you can query for various entities at that revision, retrieving a (partial) view of the database at that revision.
The library works with the latest Hibernate and Hibernate Entity Manager versions (see hibernate.org). For the versioning to work properly, the entities must have immutable unique identifiers (primary keys).
In the future, the Envers library will support versioning of arbitrary relationships. It will also include support for "revisioning groups", which will de-centralize the revisions table, if there are independend groups of entities versioned.
Another important space-saving feature will be the possibility to store only diffs between revisions, not whole properties (this of course applies only to strings).

Main features:
- versioning of basic properties (strings, integers, longs...)
- versioning of embedded components, which are composed of basic properties
- versioning of classes with simple, composite and embedded ids
- versioning of one-to-one uni- and bi-directional relations
- versioning of one-to-many bi-directional relations
- logging data for each revision using a "revision entity"
- querying historical data