Comparison between CMSynergy

Back to main page

   
SCM feature: CMSynergy Add to comparison: +CVS
+AccuRev
+Aegis
+AllChange
+Arch
+Bazaar
+BitKeeper
+ClearCase
+CM+
+Co-Op
+Darcs
+Git
+LibreSource Synchronizer
+Mercurial
+Monotone
+OpenCM
+Perforce
+PureCM
+SourceAnywhere
+Subversion
+Superversion
+Surround SCM
+svk
+Team Foundation Server
+Vesta
+Visual SourceSafe
Atomic Commits
Yes. Commits are atomic.
Files and Directories Moves or Renames
Yes. Renames are supported.
Intelligent Merging after Moves or Renames
Unknown. FILL IN.
File and Directories Copies
Yes, and it's a very cheap operation (update the target directory to include the new file/directory).
Remote Repository Replication
Yes, as long as you have the (more expensive) Distributed package.
Propagating Changes to Parent Repositories
Yes, as long as you have the (more expensive) Distributed package.
Repository Permissions
No, though a single server can serve many repositories.
Changesets' Support
Yes. Changesets (or tasks) are fundamental to the way Synergy works.
Tracking Line-wise File History
Probably, if you're a sufficiently proficient hacker with their scripting language.
Ability to Work only on One Directory of the Repository
Yes and no. Files and directories are checked out and in individually, however you have to work in the context of a project, which consists of one or more directories.
Tracking Uncommited Changes
Yes, either using integrated diff tool or user-configured external diff tool
Per-File Commit Messages
Yes.
Documentation
Medium. Lots of books, plus somewhat clunky set of HTML pages, but has some radical concepts which can cause real problems really quickly. They recommend a day's training for basic users, more for more advanced users. Took a while to become fluent.
Ease of Deployment
Medium. There is a detailed install guide for setting it up using a binary kit and a set of scripts. However it still took several tries to get it properly installed and configured. The Windows client has a slightly clunky Windows installer.
Command Set
An extensive and powerful command set, which has some CVS similarity, though the architecture is so different that it quickly moves away for anything but the basics.
Networking Support
Good (single TCP/IP socket)
Portability
Very good - various flavours of Unix, Windows (only NT family for the server), VMS, and possibly other systems.
Web Interface
Possibly.
Availability of Graphical User-Interfaces.
A couple of GUIs. A motif-based one (even on Windows) allows most functionality but is clunky. A nicer Java one allows developer work but not much administrative stuff. Has an SCCI plug-in, though it doesn't handle network problems well.
 


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.

 

Creative Commons License
This work is licensed under a Creative Commons License.