Comparison between OpenCM and svk

Back to main page

SCM feature:	OpenCM	svk	Add to comparison: +CVS +AccuRev +Aegis +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Co-Op +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +Perforce +PureCM +SourceAnywhere +Subversion +Superversion +Surround SCM +Team Foundation Server +Vesta +Visual SourceSafe
Atomic Commits	Yes. Commits are atomic.	Commits are atomic.
Files and Directories Moves or Renames	Yes. Renames are supported	Yes. Renames are supported.
Intelligent Merging after Moves or Renames	Unknown.	No. Same as Subversion.
File and Directories Copies	No. Copies are not supported.	Yes. Same as subversion.
Remote Repository Replication	No.	Yes.
Propagating Changes to Parent Repositories	No.	Yes.
Repository Permissions	Permissions are defined on a per-branch basis.	Same as subversion.
Changesets' Support	Yes. Changesets are supported.	Same as subversion.
Tracking Line-wise File History	Unknown. Probably not.	Yes. (svk blame)
Ability to Work only on One Directory of the Repository	No. All changes are made to a project as a unit	Yes.
Tracking Uncommited Changes	Yes. Using cm diff	Yes. Using svk diff
Per-File Commit Messages	Unknown.	No. There is no such feature.
Documentation	Well documented.	Relatively poor, but improving. There's a work-in-progress book as well as the Wiki and some external Articles and Tutorials.
Ease of Deployment	Very good. Install the RPM, or build from tarball and install the init script.	In addition to installing subversion, users are required to install the subversion perl bindings and a few modules from CPAN.
Command Set	A CVS-like command set that is familiar to existing CVS users.	A CVS-like command set which is easy to get used to for CVS-users.
Networking Support	Good. Uses its own proprietary client/server protocol.	Very good. svk uses SVN::Mirror to retrieve remote repository. There has been plans to add VCP support to SVN::Mirror so it will be able to mirror from arbitary remote version control systems.
Portability	Good. Portable across all UNIX systems.	Good. Clients requires subversion and its perl bindings.
Web Interface	No.	Yes. Same as Subversion.
Availability of Graphical User-Interfaces.	No GUIs are available.