Hackage :: [Package]

darcs: a distributed, interactive, smart revision control system

[ development, gpl, library ] [ Propose Tags ] [ Report a vulnerability ]

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

  • Distributed: Darcs was one of the first revision control systems in which 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, picking and choosing which patches are appropriate.

  • Smart: Darcs is different from most revision control systems in that it is based on the notion of change (or patch), rather than version. An underlying algebra of patches determines whether changes can be re-ordered. The laws of this algebra guarantee that the result of merging depends only on the final set of patches applied in a repository and not on their order.

  • Simple: As a consequence, Darcs offers a conceptually simpler view of the state of a repository: it is given by the set of patches it contains. Pulling and pushing patches merely transfers them from one set to another. So called "cherry-picking" is the default mode of operation, and it fully preserves the identity of patches.

[Skip to Readme]

Modules

[Index] [Quick Jump]

Flags

Manual Flags

NameDescriptionDefault
static

Build static binary

Disabled
threaded

Use threading and SMP support.

Enabled
executable

Build darcs executable

Enabled
rts

Support RTS options

Disabled
warn-as-error

Build with warnings-as-errors

Disabled
Automatic Flags
NameDescriptionDefault
terminfo

Use the terminfo package for enhanced console support.

Enabled

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

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

Versions [RSS] 2.1.2.1, 2.1.2.2, 2.1.98.2, 2.1.99.0, 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, 2.18.4
Change log CHANGELOG.md
Dependencies array (>=0.5.1.0 && <0.6), async (>=2.0.2 && <2.3), attoparsec (>=0.13.0.1 && <0.15), base (>=4.10 && <4.20), base16-bytestring (>=1.0 && <1.1), binary (>=0.5 && <0.11), bytestring (>=0.10.6 && <0.13), conduit (>=1.3.0 && <1.4), constraints (>=0.11 && <0.15), containers (>=0.5.11 && <0.8), crypton-connection (>=0.4 && <0.5), cryptonite (>=0.24 && <0.31), darcs, data-default-class (>=0.1.2.0 && <0.1.3), data-ordlist (>=0.4 && <0.5), directory (>=1.2.7 && <1.4), exceptions (>=0.6 && <0.11), fgl (>=5.5.2.3 && <5.9), filepath (>=1.4.1 && <1.6), hashable (>=1.2.3.3 && <1.5), haskeline (>=0.7.2 && <0.9), html (>=1.0.1.2 && <1.1), http-client-tls (>=0.3.5 && <0.4), http-conduit (>=2.3 && <2.4), http-types (>=0.12.1 && <0.12.5), memory (>=0.14 && <0.19), mmap (>=0.5.9 && <0.6), mtl (>=2.2.1 && <2.4), network (>=2.6 && <3.3), network-uri (>=2.6 && <2.8), old-time (>=1.1.0.3 && <1.2), parsec (>=3.1.9 && <3.2), process (>=1.2.3.0 && <1.7), regex-applicative (>=0.2 && <0.4), regex-base (>=0.94.0.1 && <0.94.1), regex-tdfa (>=1.3.2 && <1.4), safe (>=0.3.20 && <0.4), stm (>=2.1 && <2.6), tar (>=0.5 && <0.7), temporary (>=1.2.1 && <1.4), terminal-size (>=0.3.4 && <0.4), terminfo (>=0.4.0.2 && <0.5), text (>=1.2.1.3 && <2.2), time (>=1.9 && <1.15), tls (<2.0.0 || >=2.0.6 && <2.1), transformers (>=0.4.2.0 && <0.7), unix (>=2.7.1.0 && <2.9), unix-compat (>=0.6 && <0.8), utf8-string (>=1 && <1.1), vector (>=0.11 && <0.14), Win32 (>=2.4.0 && <2.14), zip-archive (>=0.3 && <0.5), zlib (>=0.6.1.2 && <0.8) [details]
License GPL-2.0-or-later
Author David Roundy <droundy@darcs.net>, <darcs-devel@darcs.net>
Maintainer <darcs-devel@darcs.net>
Category Development
Home page http://darcs.net/
Source repo head: darcs get http://darcs.net/
Uploaded by bfrk at 2024-10-26T10:13:37Z
Distributions Arch:2.18.3, 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 52910 total (359 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.18.4

[back to package description]

About

Darcs is a distributed version control system written in Haskell.

Building

To build and install the latest release, use

cabal update && cabal install darcs

with a recent cabal (version 3.2 or later is recommended). Any version of ghc from 8.2 up to 9.8 should work.

From inside a clone or a source dist, use

> cabal build

Cabal will tell you where the resulting darcs binary is. If you'd rather use cabal install and you are in a clone (not a source dist), you first have to generate the version info, like this:

> runghc release/gen-version-info.hs
> cabal install

Building/installing with stack used to work with a few tweaks, but is no longer officially supported due to lack of manpower. If this inconveniences you, consider contributing patches to maintain our stack.yaml.

Testing

Running the test-suite is optional, of course, but useful if you want to help find bugs or before you contribute patches. The easiest and most flexible way to do this is

> cabal configure --enable-tests
> cabal run darcs-test -- [options for darcs-test, try --help]

Using

To clone a repository via HTTP and send patches by mail:

> darcs clone --lazy http://darcs.net
> # edit files...
> darcs add my_new_file
> darcs record -m "my changes"
> darcs send

To clone via SSH and push patches:

> darcs clone user@hub.darcs.net:user/repo
> # edit files...
> darcs add my_new_file
> darcs record -m "my changes"
> darcs push

To create a project and start working:

> darcs init my_project
> cd my_project
> # create and edit files...
> darcs add my_new_file
> darcs record -m "initial version"

Pull new patches from upstream:

> darcs pull

Documentation

Concise and up-to-date documentation is available from darcs itself:

> darcs help # list all commands
> darcs help command # help for specific command
> darcs command --help # dito

The complete documentation is available as a man page which can be generated using

darcs help manpage > darcs.1

Reporting bugs

Please send bug reports to bugs@darcs.net. This will automatically add your report to the bug tracker. If you are unsure or just have a question or a comment, you can subscribe to darcs-users@darcs.net and post your question or comments there. See http://darcs.net/MailingLists for details.

There is also an IRC channel named #darcs on freenode.net, where you can report problems or ask questions.

Hacking

We are happy to receive patches and will try our best to review them in a timely fashion. Just record your patches in a clone of http://darcs.net/screened and darcs send them. You are encouraged, but not required, to look at http://darcs.net/Development/GettingStarted for additional information.

BTW, the wiki is a darcs repo, you can clone it with:

> darcs clone --lazy http://darcs.net/darcs-wiki

to edit the contents and send us patches.