Comparison between SourceAnywhere and Darcs

Back to main page

   
SCM feature: SourceAnywhere Darcs Add to comparison: +CVS
+AccuRev
+Aegis
+AllChange
+Arch
+Bazaar
+BitKeeper
+ClearCase
+CM+
+CMSynergy
+Co-Op
+Git
+LibreSource Synchronizer
+Mercurial
+Monotone
+OpenCM
+Perforce
+PureCM
+Subversion
+Superversion
+Surround SCM
+svk
+Team Foundation Server
+Vesta
+Visual SourceSafe
Atomic Commits
Yes. Commits are atomic.
Files and Directories Moves or Renames
Yes. Both moves and renames are supported, while maintaining history. Yes. Renames are supported.
Intelligent Merging after Moves or Renames
Unknown. FILL IN. Unknown.
File and Directories Copies
Copying doesn't retain history, moving does. No. Copies of files and directory structures 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. Yes.
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. Yes. Changesets are supported.
Tracking Line-wise File History
Yes. (SAW annotate) Yes. (darcs annotate)
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. It is possible to commit only a certain directory. However, one must check out the entire repository as a whole.
Tracking Uncommited Changes
Yes. Using saw diff. Yes, using "darcs whatsnew".
Per-File Commit Messages
No. There is no such feature. No.
Documentation
Good. There's an overview and tutorial on the web site, and integrated help for every command. Good. The manual contains a brief tutorial and a solid reference. Every sub-command can print its usage. Because the command-set is small and the model is simple, many users find it easy to get started.
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. Very good. darcs requires few external libraries, however you need the Glasgow Haskell Compiler if you cannot find a binary. To start working, just "darcs init".
Command Set
Very extensive but not compatible with CVS. The command set is fairly compact and the core commands are easy to understand. Follows CVS in a few places, but since the model is different most commands are unique.
Networking Support
Good. (single TCP/IP socket) Good. Darcs supports getting patches over HTTP, and getting and sending patches over SSH and email.
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. Very good. Supports many UNIXes, Mac OS X, and Windows, and is written in a portable language.
Web Interface
Currently not. darcs.cgi is included in the distribution.
Availability of Graphical User-Interfaces.
The system is GUI-based by design. None to speak of. (There is a modest graphical interface to a few commands in the distribution, but it is not being developed currently.)
 


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.