darcs: a distributed, interactive, smart revision control system

[ development, gpl, library ] [ Propose Tags ]

Darcs is a free, open source revision control system. It is:

  • Distributed: Every user has access to the full command set, removing boundaries between server and client or committer and non-committers.

  • Interactive: Darcs is easy to learn and efficient to use because it asks you questions in response to simple commands, giving you choices in your work flow. You can choose to record one change in a file, while ignoring another. As you update from upstream, you can review each patch name, even the full "diff" for interesting patches.

  • Smart: Originally developed by physicist David Roundy, darcs is based on a unique algebra of patches.

This smartness lets you respond to changing demands in ways that would otherwise not be possible. Learn more about spontaneous branches with darcs.

[Skip to Readme]




Automatic Flags

Use libcurl for HTTP support.


Use libcurl's HTTP pipelining.


Use libwww for HTTP support.


Use the pure Haskell HTTP package for HTTP support.


Use the external bytestring package.


Use the external zlib binding package.


Use the haskeline package for command line editing support.


Use the terminfo package for enhanced console support.


Use libcurses for enhances console support.


Use GADT type witnesses.


Use ansi color escapes.


Use -f <flag> to enable a flag, or -f -<flag> to disable that flag. More info


Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees


Versions [RSS],,,, 2.2.0, 2.2.1, 2.3.0, 2.3.1, 2.4, 2.4.1, 2.4.3, 2.4.4, 2.5, 2.5.1, 2.5.2, 2.8.0, 2.8.1, 2.8.2, 2.8.3, 2.8.4, 2.8.5, 2.10.0, 2.10.1, 2.10.2, 2.10.3, 2.12.0, 2.12.1, 2.12.2, 2.12.3, 2.12.4, 2.12.5, 2.14.0, 2.14.1, 2.14.2, 2.14.3, 2.14.4, 2.14.5, 2.16.1, 2.16.2, 2.16.3, 2.16.4, 2.16.5, 2.18.1, 2.18.2, 2.18.3
Dependencies array (>=0.1 && <0.3), base (<4), bytestring (>=0.9.0 && <0.10), containers (>=0.1 && <0.3), directory (>=1.0 && <1.1), filepath (>=1.1 && <1.2), haskeline (>=0.3.1 && <0.4), html (>=1.0 && <1.1), HTTP (>=3000.0 && <3001.1), mtl (>=1.1 && <1.2), network (>=2.2 && <2.3), old-time (>=1.0 && <1.1), parsec (>=2.1 && <2.2), process (>=1.0 && <1.1), random (>=1.0 && <1.1), regex-compat (>=0.71 && <=0.92), terminfo (>=0.2.2 && <0.3), unix (>=2.3 && <2.4), zlib (>=0.5 && <0.6) [details]
License LicenseRef-GPL
Author David Roundy <droundy@darcs.net>, <darcs-users@darcs.net>
Maintainer <darcs-users@darcs.net>
Category Development
Home page http://darcs.net/
Source repo head: darcs get http://darcs.net/
Uploaded by PetrRockai at 2009-01-15T21:09:11Z
Distributions Arch:2.18.1, Debian:2.14.5, Fedora:2.16.5, FreeBSD:2.10.1, NixOS:2.18.3
Reverse Dependencies 2 direct, 0 indirect [details]
Executables darcs
Downloads 51841 total (257 in the last 30 days)
Rating 2.5 (votes: 3) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs uploaded by user
Build status unknown [no reports yet]

Readme for darcs-2.2.0

[back to package description]
This is the source tree for darcs, a distributed version control system
written in Haskell.

For more information, visit the darcs web site:


Compilation and Installation

Darcs currently supports two build systems: a traditional autotools-
based system, and an experimental cabal-based system.  Currently
AUTOTOOLS IS RECOMMENDED; in later releases it will be deprecated and
eventually removed (in favour of cabal).

If a "configure" file is present, autotools is supported.  If a
"Setup.lhs" file is present, cabal is supported.  Currently there is a
separate source tarball for each build system; either can be used in
unstable checkouts.

Using Autotools

If you have the normal, autotools-based tarball, this sequence should work
for you (if you are in doubt, this is likely the case):

    $ ./configure
    $ make
    # make install

You first need to run `autoconf` if you obtained the source tree from the
darcs repository (but this is not needed for release tarballs).

For more information, please see the manual:

 * http://www.darcs.net/manual
 * doc/manual/darcs.ps

Using Cabal

This method requires the cabal package, version 1.6 or higher.  The
cabal-install package is also recommended.

If you have the "cabal-install" package on your system (that is, there
is a "cabal" executable in your path), you can use the following
commands to create an executable in ~/.cabal/bin/darcs.

    $ cabal configure
    $ cabal build
    $ cabal install

Otherwise, if you have the "cabal" package but not the "cabal-install"
package, run the following:

    $ runghc Setup configure
    $ runghc Setup build
    $ sudo runghc Setup install

You may also omit the last step and copy the darcs executable (found in
dist/build/darcs/darcs) to a location of your choosing.

More detailed instructions can be found at
including instructions on obtaining a copy of cabal-install.

Please also note that the cabal-based build by default requires the cURL
library (and development headers). If, for some reason, you cannot provide
cURL, please pass "-f-curl" to the configure step above.

For more information about darcs hacking and best practices please check
the darcs wiki at http://darcs.net/DarcsWiki

Of particular interest are the following documents:
  * http://wiki.darcs.net/index.html/DeveloperFAQ
  * http://wiki.darcs.net/index.html/DeveloperTips

For more information about the test suite, including how to run specific
tests please read tests/README.test_maintainers.txt.

Happy hacking!