|Original author(s)||Thomas Lord|
|Discontinued||1.3.5 / July 20, 2006|
|Development status||Security fixes only|
|Operating system||GNU/Linux, Windows, Mac OS X|
GNU arch software is a distributed revision control system that is part of the GNU Project and licensed under the GNU General Public License. It is used to keep track of the changes made to a source tree and to help programmers combine and otherwise manipulate changes made by multiple people or at different times.
As of 2009, GNU arch's official status is deprecation, and only security fixes are applied. Bazaar (or 'bzr') has since also been made an official GNU project and can thus be considered the replacement for GNU arch. It is not a fork of Arch.
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.
- 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. In 2003, arch became part of the GNU project.
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.
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. However, this did not happen: the Baz fork was abandoned by Canonical in favour of the separate Bazaar project, with the 1.5 release of Baz being scrapped in 2006. In October, 2005, Andy Tai announced that Lord and the Free Software Foundation had accepted his offer to be the maintainer of GNU arch. 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 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. It was announced in June 2005, the first pre-release was in July and the last in August, just prior to Lord's resignation as maintainer. revc only had 10 core commands and Lord intended to eliminate restrictive namespaces, complicated filenaming conventions and increase the speed.
Perhaps the most common criticism of GNU arch is that it is difficult to learn, even for users who have experience with other SCM 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.
Some also criticize GNU arch for using very unusual file naming conventions ("FunkyFileNames" at the Wayback Machine (archived August 8, 2007)), 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.
- Tai, Andy (2008-03-28). "Re: revc". gnu-arch-users (Mailing list). Retrieved 2008-06-17.
- "History of Bazaar". Retrieved 20 May 2014.
- Moffit, Nick (2004-11-01). "Revision Control with Arch: Introduction to Arch". Linux Journal. Retrieved 2008-06-18.
- Lord, Tom (2003-07-13). "GNU, doc foo, short-term plans, hacking suggestions, money". arch-users (Mailing list). Retrieved 2008-06-18.
- Lord, Thomas (2004-10-31). "community spirit". gnu-arch-users (Mailing list). Retrieved 2008-06-17.
- Lord, Thomas (2005-08-15). "GNU Arch maintainership". gnu-arch-users (Mailing list). Retrieved 2008-06-17.
- "Baz1x - Bazaar Version Control". 2006-07-24. Retrieved 2008-01-17.
- Arbash Meinel, John; Aaron Bentley; Martin Pool; Mark Shuttleworth (2006-07-26). "HistoryOfBazaar". Retrieved 2008-02-20.
- Collins, Robert (2006-06-30). "releasing 1.5". bazaar-old (Mailing list). Retrieved 2007-06-16.
- Tai, Andy (2005-10-27). "Re: Good News about GNU Arch!". gnu-arch-users (Mailing list). Retrieved 2008-06-17.
- Lord, Thomas (2005-06-20). "arch 2.0 code base in progress". gnu-arch-dev (Mailing list). Retrieved 2008-06-17.
- Lord, Thomas (2005-07-08). "GNU Arch 2.0 -- first source". gnu-arch-dev (Mailing list). Retrieved 2008-06-17.
- Lord, Thomas (2005-08-01). "Arch 2.0 release (revc.0.0x2)". gnu-arch-users (Mailing list). Retrieved 2008-06-17.
- Wandrebeck, Laurent (2008-03-26). "revc". gnu-arch-users (Mailing list). Retrieved 2008-06-17.
- Lord, Thomas (2008-03-28). "Re: revc". gnu-arch-users (Mailing list). Retrieved 2008-06-17.
- Pool, Martin (2004-06-21). "What's wrong with Arch?". Retrieved 2008-06-18.
- Pool, Martin (2004-09-26). "Tom Lord interview, and related things". Retrieved 2008-06-18.
Earlier versions were very much bound into projects being run the way Tom wanted them: wierd file conventions, only committing from clean trees, and so on
- Weimer, Florian (2004-06-09). "Some Issues with GNU arch". Retrieved 2008-06-18.