The darcswatch package

[Tags: gpl, program]

DarcsWatch is a tool to track the state of darcs patches that have been submitted to some project, usually by using the darcs send command. It allows both submitters and project maintainers to get an overview of patches that have been submitted but not yet applied. Some notable features are:

[Skip to ReadMe]


Versions0.1, 0.2, 0.3, 0.4, 0.4.1, 0.4.2, 0.4.3, 0.4.4
Change logNone available
Dependenciesbase (>3 && <4), bytestring, containers, Crypto, directory, filepath, HTTP (>=4000), nano-md5, network, old-time, parsec, unix, xhtml, zlib [details]
AuthorJoachim Breitner
MaintainerJoachim Breitner <>
Home page
Source repositoryhead: darcs get
this: darcs get --tag v0.1
UploadedWed Jan 21 22:15:59 UTC 2009 by JoachimBreitner
Downloads1357 total (41 in last 30 days)
0 []
StatusDocs not available [build log]
All reported builds failed as of 2015-11-17 [all 4 reports]


Maintainers' corner

For package maintainers and hackage trustees

Readme for darcswatch-0.1


© 2008 Joachim Breitner <>

This program tracks darcs patches and repositories, giving
an overview over their state (applied or not applied).

The patches are expected to come in via the
program, which stores the patches in the appropriate place.

The main program then downloads the repository inventories
and compares the mailed patches against the repository. It
summaries their status per submitter and per repository.

The program expects a directory as a parameter and will read
the config file therein for configuration. An example
configuration is included.

darcsweb uses modules from these non-standard packages:
 * xhtml
 * network
 * Crypto
 * parsec
 * nano-md5
 * zlib

There are a lot of open issues, and help is very
appreciated. A non exclusive list of TODO items is:

 * Nicer output (CSS magic!)
 * (Maybe) Add repositories per GnuPG signed command

When committing patches, please make sure that they work with
the version of GHC in the latest Debian stable release, at
the moment ghc6.6, and compatible libraries.

BTW, the simple darcs repository parsing code might be useful for
other projects as well. I try to keep the patches for the Darcs.hs
related stuff separate from the rest, so you can select them when
"darcs pull"ing. If you also follow this procedure, we can share the
Darcs.hs code between projects, by making sure our patches to these
files can be shared without dragging in the rest of the project.