| SCM feature: | AccuRev | PureCM |
Add to comparison:
+CVS +Aegis +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +OpenCM +Perforce +SourceAnywhere +Subversion +Superversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe |
|---|---|---|---|
|
Atomic Commits |
Yes. Commits are atomic | Yes. Commits are atomic. | |
|
Files and Directories Moves or Renames |
Yes. Renames of both files and directories are supported. Supports controlling of symbolic links as well. | Yes. File and folder renames and moves are directly supported. | |
|
Intelligent Merging after Moves or Renames |
Unknown. FILL IN. | Yes, intelligent renames are supported. | |
|
File and Directories Copies |
Copying is supported through symbolic links (but all linked files are treated as the same file version). Moves are fully supported with the history retained. | Yes. Copies are supported. | |
|
Remote Repository Replication |
Yes. | Yes. Using the PureCM Proxy Server. | |
|
Propagating Changes to Parent Repositories |
With AccuReplica, the replica server has all the meta-data and fetches file data as needed by replica users; all write operations pass automatically from the replica to the master server. | No. | |
|
Repository Permissions |
Yes. Access can be defined per stream (branch) using access control lists. | Yes. Permissions can be set against repositories, streams (branches/labels), folders and files using Access Control Lists. | |
|
Changesets' Support |
Yes, AccuRev provides robust functionality for change sets (called change packages in AccuRev) including viewing differences by change packages and merging changes from stream to stream by change package. | Yes. Changesets are supported. | |
|
Tracking Line-wise File History |
Yes. Available from both the gui and cli. | Yes, annotation is available through the GUI. | |
|
Ability to Work only on One Directory of the Repository |
Yes. AccuRev provides functionality to define feature streams in which only the subset of code is seen. A group of developers can then be retricted to work only from that stream so they are only allowed to check in changes to that subset of code. | Yes. | |
|
Tracking Uncommited Changes |
Yes. The functionality is available through both the GUI and the command line interface. | Yes. | |
|
Per-File Commit Messages |
No. Commit messages are per change. | No. Commit messages are per change. | |
|
Documentation |
Excellent. There is a full set of documentation available in pdf format available at AccuRev Documentation as well as context-sensitive help in the GUI. | Very Good (html and command line help) | |
|
Ease of Deployment |
Excellent. All that is required is to download the binaries for the appropriate platform and run the installer. The installation package is self-contained. No additional software is needed. AccuRev supports most UNIX, Linux, and Windows platforms and deploying AccuRev to a multi-platform environment is straight-forward. | Very good. PureCM is very easy to deploy. | |
|
Command Set |
Very extensive but not compatible with cvs. | A CVS-like command set which is easy to get used to for CVS-users. | |
|
Networking Support |
Good. (proprietary protocol using TCP/IP) | Good. (single TCP/IP socket) | |
|
Portability |
Excellent. The server runs on most UNIX, Linux and Windows platforms. The client runs on all of these platforms and on Mac OS X. | Excellent. Client and Server run on Windows, Linux, Solaris and other UNIXes. The client also runs on Mac OS X. | |
|
Web Interface |
No. | Yes. | |
|
Availability of Graphical User-Interfaces. |
A single, comprehensive, java-based GUI is provided. The GUI has the same look-and-feel on all platforms. | Cross-platform GUI for Windows, Linux, Mac OS X and other UNIXes. | |
|
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. |
|