| SCM feature: | SourceAnywhere | Superversion |
Add to comparison:
+CVS +AccuRev +Aegis +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +OpenCM +Perforce +PureCM +Subversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe |
|---|---|---|---|
|
Atomic Commits |
Yes. Commits are atomic. | Commits are atomic. | |
|
Files and Directories Moves or Renames |
Yes. Both moves and renames are supported, while maintaining history. | No. Renames are not supported. | |
|
Intelligent Merging after Moves or Renames |
Unknown. FILL IN. | No. Renames are not supported. | |
|
File and Directories Copies |
Copying doesn't retain history, moving does. | No. Copies are not supported. | |
|
Remote Repository Replication |
Not directly possible with the included GUI or command line tools; Some SQL Server tool might be useable. | Yes. | |
|
Propagating Changes to Parent Repositories |
Not directly possible with the included GUI or command line tools; Some SQL Server tool might be useable. | No. | |
|
Repository Permissions |
Yes. SourceAnywhere Server Manager can define access to a repository per user or group and user access rights to a project. | No. | |
|
Changesets' Support |
Not exactly. SourceAnywhere uses a related concept of configurations instead, which some has similar properties. | Partial support. Changes are grouped into changesets, but cannot be cancelled invididually yet. | |
|
Tracking Line-wise File History |
Yes. (SAW annotate) | No. | |
|
Ability to Work only on One Directory of the Repository |
Yes. SourceAnywhere can define the user access right to each project and users can be restricted to work only on the projects they have check out/in right. | No. | |
|
Tracking Uncommited Changes |
Yes. Using saw diff. | Yes. Local changes are detected and shown immediately. Changes can be collected in a local buffer before being committed to the repository. | |
|
Per-File Commit Messages |
No. There is no such feature. | Yes. | |
|
Documentation |
Good. There's an overview and tutorial on the web site, and integrated help for every command. | Fairly poor. There are two tutorials, but there is no reference. Installing and getting started with the GUI is very easy though. | |
|
Ease of Deployment |
Excellent. Dynamsoft SourceAnywhere is extremely easy to install. It is totally written in C++ from scratch, which means that you don't need any additional components and frameworks to support the installation. | If Java 1.4 is installed, deployment of Superversion usually takes two clicks. | |
|
Command Set |
Very extensive but not compatible with CVS. | There is little need to memorize a command set because all actions take place in a GUI. A part of the terminology used in the application is borrowed from CVS. | |
|
Networking Support |
Good. (single TCP/IP socket) | Good. Network support based on RMI is integrated seamlessly. Encryption and HTTP tunnelling are planned for the near future. | |
|
Portability |
Good. The server runs on Windows only. Clients can work on any platform that SWT (Standard Widget Toolkit) supports, including Windows, Linux, Mac, Solaris, AIX, HP-UX, SCO Unix, FreeBSD and so on. | Excellent. Clients and servers work on any Java 1.4-compatible platform. There is official support for Windows, Linux and OS/2. | |
|
Web Interface |
Currently not. | No. | |
|
Availability of Graphical User-Interfaces. |
The system is GUI-based by design. | A GUI is integrated. | |
|
Information taken from Better SCM Initiative website by Shlomi Fish (shlomif@iglu.org.il). Reorganized for usability by Alexey Mahotkin (Version Control Blog) in 2008. |
|