darcs
Darcs is an advanced revision control system. It has two particularly distinctive features which differ from other revision control systems: each copy of the source is a fully functional branch, and underlying it is a consistent and powerful theory of patches. In spite of its power, darcs is simple to use, in part because of the symmetry that is restored by making each copy of the repository a branch.
| Tags | Software Development Version Control |
|---|---|
| Licenses | GPL |
| Operating Systems | Windows Windows Mac OS X POSIX |
| Implementation | Haskell |
Recent releases
- 22 Nov 2008 00:43
Changes: This release provides GHC 6.10 support and fixes a crash on Windows with the darcs help command.
- 22 Nov 2008 00:43
Changes: This version provides over 40 bugfixes and 20 new features since 2.0.2. The most notable changes are defaulting to darcs-2 format repositories, better HTTP support, and repository correctness (fixes to the pending patch).
- 02 Aug 2005 03:58
Changes: This release adds numerous optimizations and minor bugfixes. Darcs now scales much better to large repositories, and performs much better on huge files with many changes. "Darcs changes" has been extended to allow display of entire patches with the --verbose flag. Experimental support for working with Git repositories has been added.
- 25 May 2005 08:08
Changes: A number of bugs that were present in version 1.0.2 have been fixed. Most particularly, there was a (generally harmless) bug in darcs 1.0.2 which led to a frightening message about an error in writing pending changes. Besides bugfixes, there were also some interface enhancements, including an improved unpull/unrecord patch selection interface and finer-grained control over colorization and character escaping in darcs' output.
- 05 Feb 2005 13:07
Changes: There were no changes made since the last release candidate (1.0.2rc4). Several moderately serious bugs were fixed that were present in darcs 1.0.1. In addition, a few minor documentation and error message improvements were made, and an option was added to set the executable bit properly for scripts.
- All comments
Recent commentsBuilding on panther
Building on Panther fails. Sometimes I get:
/SourceCache/gnumake/gnumake-108/make/expand.c:523: failed assertion `current_variable_set_list->next != 0'
Abort
Sometimes:
ghc -cpp -I/sw/include -L/sw/lib -I. -package unix -package text -O -funbox-strict-fields -package util -c Lcs.lhs
Lcs.lhs:43:
Failed to load interface for `FastPackedString':
Could not find interface file for `FastPackedString'
(use -v to see a list of the files searched for)
make: *** [Lcs.o] Error 1
I have GHC-6.2. I wish it had a fink package.
Re: Like your project, like your way of implementing it, but....
Then my only suggestion would be to try the rpm for darcs, which is completely untested, as I don't have an RPM-based system myself, or to go throught the pain of compiling ghc.
Re: Like your project, like your way of implementing it, but....
> Did you try the RPMs provided for RedHat
> at http://www.haskell.org/ghc? I imagine
> one of them might work with Mandrake.
Yes, it failed.
Re: Like your project, like your way of implementing it, but....
> Isn't there a simple way to create self-contained binaries for GHC?
Did you try the RPMs provided for RedHat at http://www.haskell.org/ghc? I imagine one of them might work with Mandrake.
Like your project, like your way of implementing it, but....
The centralized CVS-archive works ok if you are connected to the internet all the time, but often I have 2 computers next to each other, no one of them connected to the internet. So I was willing to try darcs.
Also, using Haskell for implementation gives credibility, I expect the system to work. I do not understand why not more tools are implemented using advanced languages, all this C-coding in is rather improductive and there is a big risks for buggy software.
So, I decided to install and try it. However, getting GHC to run on Mandrake 9.1 wasn't easy, and I aborted.
Isn't there a simple way to create self-contained binaries for GHC? If you cannot get a simple way to distribute it, people will get the impression that you need to use C/Perl/PHP to be able to install it anywhere, and not languages like Haskell.