Comparison between PureCM

Back to main page

   
SCM feature: PureCM Add to comparison: +CVS
+AccuRev
+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.
Files and Directories Moves or Renames
Yes. File and folder renames and moves are directly supported.
Intelligent Merging after Moves or Renames
Yes, intelligent renames are supported.
File and Directories Copies
Yes. Copies are supported.
Remote Repository Replication
Yes. Using the PureCM Proxy Server.
Propagating Changes to Parent Repositories
No.
Repository Permissions
Yes. Permissions can be set against repositories, streams (branches/labels), folders and files using Access Control Lists.
Changesets' Support
Yes. Changesets are supported.
Tracking Line-wise File History
Yes, annotation is available through the GUI.
Ability to Work only on One Directory of the Repository
Yes.
Tracking Uncommited Changes
Yes.
Per-File Commit Messages
No. Commit messages are per change.
Documentation
Very Good (html and command line help)
Ease of Deployment
Very good. PureCM is very easy to deploy.
Command Set
A CVS-like command set which is easy to get used to for CVS-users.
Networking Support
Good. (single TCP/IP socket)
Portability
Excellent. Client and Server run on Windows, Linux, Solaris and other UNIXes. The client also runs on Mac OS X.
Web Interface
Yes.
Availability of Graphical User-Interfaces.
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.

 

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