darcs: a distributed, interactive, smart revision control system

This is a package candidate release! Here you can preview how this package release will appear once published to the main package index (which can be accomplished via the 'maintain' link below). Please note that once a package has been published to the main package index it cannot be undone! Please consult the package uploading documentation for more information.

[maintain] [Publish]

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


[Skip to Readme]

Properties

Versions 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.4, 2.16.5, 2.18.1, 2.18.2
Change log CHANGELOG
Dependencies array (>=0.5.1.0 && <0.6), async (>=2.0.2 && <2.3), attoparsec (>=0.13.0.1 && <0.14), base (>=4.10 && <4.15), base16-bytestring (>=0.1.1.7 && <1.1), binary (>=0.5 && <0.11), bytestring (>=0.10.6 && <0.11), conduit (>=1.3.0 && <1.4), constraints (>=0.11 && <0.13), containers (>=0.5.6.2 && <0.7), cryptonite (>=0.24 && <0.28), darcs, data-ordlist (>=0.4 && <0.5), directory (>=1.2.7 && <1.4), fgl (>=5.5.2.3 && <5.8), filepath (>=1.4.1 && <1.5.0.0), hashable (>=1.2.3.3 && <1.4), haskeline (>=0.7.2 && <0.9), html (>=1.0.1.2 && <1.1), http-conduit (>=2.3 && <2.4), http-types (>=0.12.1 && <0.12.4), memory (>=0.14 && <0.16), mmap (>=0.5.9 && <0.6), mtl (>=2.2.1 && <2.3), network (>=2.6 && <3.2), 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-compat-tdfa (>=0.95.1 && <0.96), stm (>=2.1 && <2.6), tar (>=0.5 && <0.6), temporary (>=1.2.1 && <1.4), terminfo (>=0.4.0.2 && <0.5), text (>=1.2.1.3 && <1.3), time (>=1.5.0.1 && <1.10), transformers (>=0.4.2.0 && <0.6), unix (>=2.7.1.0 && <2.8), unix-compat (>=0.5 && <0.6), utf8-string (>=1 && <1.1), vector (>=0.11 && <0.13), Win32 (>=2.4.0 && <2.7), zip-archive (>=0.3 && <0.5), zlib (>=0.6.1.2 && <0.7.0.0) [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 2021-05-20T19:18:12Z

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
curl

Use libcurl for HTTP support.

Disabled
pkgconfig

Use pkgconfig to configure libcurl

Disabled
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


Readme for darcs-2.16.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 8.10 should work.

From inside a clone or a source dist, use

> cabal build

or

> cabal install

If you prefer stack:

> stack install

Note that using stack will select older versions for some dependencies, which may mean that performance is slightly less than optimal.

Running the test suite

This is optional, of course, but useful if you want to help find bugs or before you contribute patches.

> cabal build --enable-tests
> cabal test --test-show-details=direct

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.