[darcs-users] Darcs Wiki Engine

[Max Battcher]

Trent W. Buck wrote:
> 5) The CLI is does not have some useful functions that applications
>    could leverage.
> 
> For example, a whole swag of visualization tools would be easier if
> there was an easy way to find out if there was any dependency relation
> between two patches X and Y, and if so, what kind of relation it is.
> 
> The only way I've seen that done by a darcs CLI-using script is to
> repeatedly pull and unpull patches from a repository, taking note of
> which patches are skipped.  This approach was something like O(n²) or
> possibly O(nⁿ) time; certainly it wasn't usable for a repository with
> more than a couple of hundred patches.
> 
> Similarly, I can't think of an easy way to answer questions about
> conflictors like "with which hunks, in which patches, does this |: hunk
> conflict?" using the command-line interface.
> 
> Maybe Darcs could have such utilities built-in, but I'm not sure it's
> the Right Thing for a version control system to include code for
> emitting Graphviz graph definitions, for example.

Maybe not to Graphviz specifically, but both those questions might be 
useful some how as show subcommands with maybe a very simple ASCII 
output and a very nice digestible --xml-output for the tools that do 
want to convert it to some visual graph system...

If it's useful to a third-party application it still may be useful for 
CLI output of some sort.

--
--Max Battcher--
http://worldmaker.net