[darcs-users] Darcs dependencies - how are they stored and discovered?

Matt Lamari matt.lamari at gmail.com
Thu Jul 12 19:58:20 UTC 2012



Are obliterate and pull (dry run) the 2 cardinal tools for examining
dependencies?  Are their costs equivalent views on the same core
calculation (from different sides)?  Is there anything else I should
investigate if interested in dependencies?

On 7/12/2012 10:16 AM, Michael Hendricks wrote:
> Hi Matt.  Darcs normally doesn't store dependencies directly.  They're
> calculated based on whether patches can commute with on another.  If
> they freely commute, there's no dependency; otherwise there is one.
>
> One exception is dependencies recorded by `darcs record --ask-deps`
> which lets the user manually add explicit dependencies.  These are
> store on disk as part of the newly recorded patch.
>
> To answer your question, I don't think using the library directly will
> make patch dependency calculations much faster.
>
> -- 
> Michael



More information about the darcs-users mailing list