Comparison between Aegis and Co-Op

Back to main page

SCM feature:	Aegis	Co-Op	Add to comparison: +CVS +AccuRev +AllChange +Arch +Bazaar +BitKeeper +ClearCase +CM+ +CMSynergy +Darcs +Git +LibreSource Synchronizer +Mercurial +Monotone +OpenCM +Perforce +PureCM +SourceAnywhere +Subversion +Superversion +Surround SCM +svk +Team Foundation Server +Vesta +Visual SourceSafe
Atomic Commits	Commits are atomic.	Yes. Commits are atomic.
Files and Directories Moves or Renames	Yes. Renames are supported.	Renames of files are supported. Renaming a directory requires creating a new one, moving the files and deleting the old one. Moved file histories are preserved.
Intelligent Merging after Moves or Renames	Unknown. FILL IN.	Unkown. FILL IN.
File and Directories Copies	No. Copies are not supported.	Copying doesn't retain history, moving does.
Remote Repository Replication	Yes.	Repositories are always replicated on local machines. There is no central server.
Propagating Changes to Parent Repositories	Yes.	It's a peer-to-peer system, which keeps all replicas of the repository in sync.
Repository Permissions	Yes. Aegis relies on the UNIX permissions system to implement permissions for files in the repository.	First access (joining the project) requires administrator's approval. Subsequent access to that project is not controlled.
Changesets' Support	Yes. Changesets are supported.	Yes. Changesets are the default.
Tracking Line-wise File History	Yes. aeannotate	Not directly, but it's possible to compare any two versions using a visual differ.
Ability to Work only on One Directory of the Repository	No. All changes are made repository-wide.	No. All changes are made to a project as a unit, but it's possible to access each file's history separately.
Tracking Uncommited Changes	Yes. Using aediff.	Yes, using built-in visual differ/editor.
Per-File Commit Messages		No. Commit messages are per change. They go to all project members and update their repositories.
Documentation	Medium. The documentation is given in several large scope troff documents, that are only usable as not-so-PDFish PDF documents, and as text documents that lack any formatting. It is very hard to get started using it with the online resources. The content is of good quality, but otherwise not made very accessible.	Very good. Step-by-step tutorial and HTML help is included.
Ease of Deployment	The Aegis binary should be installed as SUID-root, and so requires root privileges to install. It also not very portable to Win32 systems. Other than that, Aegis supports an easy autoconf or RPM/apt-based installation process.	Very easy to deploy, since there is no central server. Can be configured to use e-mail or LAN (or both) for synchronization. For e-mail, requires MAPI-compliant e-mail client.
Command Set	A complex command set that involves many operations just to get started. Not CVS-compatible. (albeit support for such basic operations was contemplated) Note that Aegis is a Software Configuration Management system and not just a simple version control system, which may justify this extra complexity.	Basic commands are compatible with CVS.
Networking Support	Poor. Aegis is filesystem-oriented and so can be networked only via NFS (network file-system) or a similar protocol. There exists some HTTP-functionality, but it is quite limited.	Uses the simplest LAN interface: copying files between shared directories.
Portability	Medium. The source is portable across all UNIXes, but the Windows version work only using cygwin, and even then not entirely natively.	Windows only: starting with Win95.
Web Interface	Yes.	Since this functionality is always available locally, there is no need for web interface.
Availability of Graphical User-Interfaces.	There is tkaegis.	The system is GUI-based by design.