Comparison between Arch

Back to main page

SCM feature:	Arch	Add to comparison: +CVS +AccuRev +Aegis +AllChange +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +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	Yes. Renames can be merged intelligently.
File and Directories Copies	No. Copies of files and directory structures are not supported.
Remote Repository Replication	Yes.
Propagating Changes to Parent Repositories	Yes.
Repository Permissions	Yes. It is possible to define permissions on access to different parts of a remote repository based on the permission systems of the underlying protocol.
Changesets' Support	Yes. Changesets are supported.
Tracking Line-wise File History	Not in the command line client, but ViewARCH, a web-interface for Arch, has it.
Ability to Work only on One Directory of the Repository	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 "tla changes".
Per-File Commit Messages	No.
Documentation	Medium. There are two online tutorials and a comprehensive online documentation. The command line client also supplies a reference page. However, some of the documentation is out of date or incomplete.
Ease of Deployment	Excellent. An arch service is nothing but a filesystem-space hosted by any of its supported protocols (FTP, SFTP, WebDAV, etc.). The arch client is written in C, and is portable across UNIX systems (and on Win32 only with a UNIX emulation layer).
Command Set	Many commands are compatible with CVS or BitKeeper. However, there are many other commands for it for different uses. Aliasing of commands is possible so it it may be possible to make it more compatible.
Networking Support	Excellent. Arch can utilize a multitude of protocols for its service, which is nothing but a dumb remote filesystem server. Currently supported protocols include FTP, SFTP, WebDAV (remote file access over HTTP), as well as any remote filesystem protocol (NFS, SMB).
Portability	Good. The source is portable across all UNIXes, but requires a UNIX emulation layer on Windows. (need to verify). A service can be hosted on any platform that sports a suitable Internet service.
Web Interface	There's ViewARCH, and ArchZoom which are works in progress.
Availability of Graphical User-Interfaces.	There are tlator, Octopy, and ArchWay and possibly others under development.