GNU arch

Features

Being a distributed, decentralized versioning system, each revision stored using arch is uniquely globally identifiable; such identifier can be used in a distributed setting to easily merge or "cherry-pick" changes from completely disparate sources.

Being decentralized means that there is no need for a central server for which developers have to be authorized in order to contribute. As with other systems, a full read-only copy of a project is made accessible in an "official" repository via HTTP, FTP, or SFTP; but then, contributors are encouraged to make modifications and publish them in a public archive (repository) of their own, so that the head developer may manually merge changesets into the official repository.

To simulate the behavior of centralized revision control systems, the head developer could allow shell access (SSH) or write access (FTP, SFTP, WebDAV) to a server, allowing authorized users to commit to a central server. More often, GNU arch-managed projects have a lead benevolent dictator that merges changes from contributors.

GNU arch has several other features:

; Atomic commits : Commits are all-or-nothing. The tree must be in proper condition before the commit begins, and commits are not visible to the world until complete. If the commit is interrupted before this, it remains invisible and must be rolled back before the next commit. This avoids corruption of the archive and other users' checked-out copies. ; Changeset oriented : Instead of tracking individual files (as in CVS), GNU arch tracks changesets, which are akin to patches. Each changeset is a description of the difference between one source tree and another, and so a changeset can be used to produce one revision from another revision. Authors are encouraged to use one commit per feature or bugfix. ; Easy branching : Branching is efficient and can span archives. A branch (or 'tag') simply declares the ancestor revision, and development continues from there. ; Advanced merging : Due to the permanent record of all ancestors and merged revisions, merging can take into account which branch contains which patch, and can do three-way merging based on a shared ancestor revision. ; Cryptographic signatures : Every changeset is stored with a hash to prevent accidental corruption. Using an external file signing program (such as GnuPG or another PGP client), these hashes can also optionally be signed, preventing unauthorized modification if the archive is compromised. ; Renaming : All files and directories can be easily renamed. These are tracked by a unique ID rather than by name, so history is preserved, and patches to files are properly merged even if filenames differ across branches. ; Metadata tracking : The permissions of all files are tracked. Symbolic links are supported and are tracked the same way as files and directories.

History and maintainership

GNU arch version 1 and tla

The original author and maintainer of GNU arch was Thomas Lord who started the project in 2001. The command used to manipulate GNU arch repositories is tla, an initialism for Tom Lord's Arch. Lord started GNU arch as a collection of shell scripts to provide an alternative to CVS.{{cite news |access-date=2008-06-18}} In 2003, arch became part of the GNU project.{{Cite mailing list |access-date=2008-06-18 |mailing-list=arch-users

The GNU arch project forked several times, resulting in both Canonical Ltd.'s now abandoned Baz fork and Walter Landry's ArX project. Both forks provoked a hostile reaction: the ArX fork was due to a serious dispute in direction and Lord was strongly critical of Canonical's approach to announcing the Baz project.{{Cite mailing list |mailing-list=gnu-arch-users |access-date=2008-06-17}}

In August 2005 Lord announced that he was resigning as the maintainer of GNU arch and recommended that Baz become the main GNU arch project.{{Cite mailing list |access-date=2008-06-17 |mailing-list=gnu-arch-users}} However, this did not happen: the Baz fork was abandoned by Canonical in favour of the separate Bazaar project,{{cite web | access-date = 2008-01-17 | archive-date = 2008-01-07 | archive-url = https://web.archive.org/web/20080107203210/http://bazaar-vcs.org/Baz1x | url-status = dead | access-date = 2008-02-20 | archive-date = 2009-02-26 | archive-url = https://web.archive.org/web/20090226181637/http://bazaar-vcs.org/HistoryOfBazaar | url-status = dead |mailing-list=bazaar-old |access-date=2007-06-16 |url-status=dead |archive-url=https://web.archive.org/web/20110512173621/https://lists.ubuntu.com/archives/bazaar-old/2006-June/000531.html |archive-date=2011-05-12 |access-date=2008-06-17 |mailing-list=gnu-arch-users}} Tai subsequently merged many features from Baz back into tla, but in March 2008 indicated that tla was no longer under active development and was no longer competitive with other version control systems.

revc

revc was a prototype revision control project by Thomas Lord that he intended to become GNU arch 2.0, designed to be a radical departure from tla and to draw many ideas from the Git revision control system.{{Cite mailing list |access-date=2008-06-17 |mailing-list=gnu-arch-dev |access-date = 2008-06-17 |mailing-list = gnu-arch-dev |archive-url = https://web.archive.org/web/20110517201422/http://osdir.com/ml/version-control.arch.devel/2005-07/msg00006.html |archive-date = 2011-05-17 |url-status = dead |access-date=2008-06-17 |mailing-list=gnu-arch-users}} revc only had 10 core commands and Lord intended to eliminate restrictive namespaces, complicated file naming conventions and increase the speed.

As of 2008 the last pre-release, 0.0x2, of revc is still available{{Cite mailing list |mailing-list = gnu-arch-users |access-date=2008-06-17}} and Lord was still interested in some of the ideas in GNU arch but did not have the resources to resume development of revc.{{Cite mailing list |access-date=2008-06-17 |mailing-list=gnu-arch-users}} Thomas Lord died in June 2022.{{Citation

Criticism

Perhaps the most common criticism of GNU arch is that it is difficult to learn, even for users who have experience with other Version control systems. In particular, GNU arch has a large number of commands, which can be intimidating for new users and some design elements arguably too strongly enforce Lord's taste in version control practices.{{cite web |archive-url=https://archive.today/20120714202439/http://sourcefrog.net/weblog/software/vc/arch/whats-wrong.html |url-status=dead |archive-date=2012-07-14 |access-date=2008-06-18 |archive-url=https://archive.today/20120713233855/http://sourcefrog.net/weblog/software/vc/arch/lord-interview.html |url-status=dead |archive-date=2012-07-13 |access-date=2008-06-18

Some also criticize GNU arch for using very unusual file naming conventions (), which can create difficulties for using it in scripts, some shells, and in porting it to non-Unix operating systems. GNU arch has been criticised for having a slow running time as part of a design decision to lessen internal code complexity.{{cite web |access-date=2008-06-18}}

References

References

1. "History of Bazaar".