ArX
ArX is a flexible, high performance, distributed revision control system featuring whole-tree atomic changesets, easy branching, and sophisticated merging. ArX has always been self hosting.
| Tags | Software Development Version Control |
|---|---|
| Licenses | GPL |
| Operating Systems | POSIX |
| Implementation | Emacs Lisp C++ |
Recent releases
- 19 Nov 2005 21:25
Changes: ArX now uses three-way merging as a default, and supports third party merge tools. ArX is also much more clever about renames. "merge" now uses the --update option instead of using heuristics. ArX now records when there are conflicts in the tree, and will not let you commit unless they are resolved. ArX now uses -v and -q for verbosity. "commit" now supports --author and --date options for Tailor. The patch queue manager has been updated, and some small bugs were fixed.
- 21 Jul 2005 01:02
Changes: "annotate" was implemented and "log" was enhanced. The patch queue was updated and tests were modified to work with ArX. "fork", "replay", and "merge" no longer support out-of-place forks. "arx help" now works. The autoconf scripts for Python configuration were revamped to use a standard autoconf macro. INSTALL.GENERIC was updated with details. Revision libraries and "library" were removed. Some limitations in "merge", "diff", and "replay" were removed.
- 06 May 2005 01:47
Changes: The licensing problems with the Boost libraries have been fixed, and binary packages of ArX are now available. "tag" has been enhanced so that you can tag the latest revision of a particular branch (floating tags), instead of just one particular revision. Plain old HTTP support has been fixed and streamlined. "merge", "fork", "export", and "diff" have seen minor changes. The manual has seen a number of improvements.
- 10 Mar 2005 21:52
Changes: Security fixes and a few new features were added. An insecure path handling issue with building configurations was fixed by removing the configuration mechanism and enhancing the capabilities of "tag" so that it can take its place. "diff" now has a recursive option, "merge" and "replay" are much simpler, "make-dist" and "init-tree" were renamed to "export" and "init", and gpg is now much less chatty.
- 24 Jan 2005 23:05
Changes: This release featured cryptographic signatures, improved mirroring, better support for plain HTTP archives, and support for OS X and Windows under Cygwin. The way that archives are registered has changed, so all archives will have to be reregistered.
- All comments
Recent commentsRe: Strongly advise avoiding this Arch fork.
Are you going to judge the software on its
merits or on the friendliness of the maintainer?
If the former, you should have omitted your slap
at Landry.
If the latter, you should have made sure to
describe Tom Lord for everyone, making sure to
point out his prickly personality, his inability
to separate the software from his radical
politics, and his unstable financial situation
which could lead to tla being abandoned at any
time.
Anyone who has to manage critical software at
some point should carefully consider both Arx
and
Arch before deciding, because you never know
when Tom Lord may decide you're antisocial and
ignore your needs, or if Lord's rumored
unemployability finally kills
his project, leaving you with the need to fork
anyway.
Re: Strongly advise avoiding this Arch fork.
For the discussion that lead to Tom Lord's entry into my killfile you can start here. If you really want the whole story, you will have to read back many months. Now that we no longer share mailing lists, I have removed him from my killfile.
Strongly advise avoiding this Arch fork.
Landry, maintainer of this fork of the Arch revision control system, is such a prickly personality as to have had Tom Lord, the originator and active maintainer of arch, *killfiled* for over a month. While Landy was active maintainer of arch as a whole (before Tom came back in), he killed features that he personally didn't use (aka thought to be too much trouble), and otherwise managed things badly.
Arch is very actively maintained, has a wider active contributer (and user) base, has an active C port with vastly better performance than the original version (tla), and is all-round a much more interesting project.
From a end-user perspective, however, both of these are vastly superior to CVS, substantially superior to Subversion (on grounds of features, stability and sane design), and without any of the evil licensing of BitKeeper (and even a spot of technical superiority here and there!). Features like {arch,arx}'s branching mechanism quickly become second nature, to the point of wishing every *other* revision control system had such support. Strongly reccomended.
By the way, I'd be curious to see if I can get a response to this from anyone *other* than Landry.