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

[Michael Hendricks]

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


On Thu, Jul 12, 2012 at 9:14 AM, Matt Lamari <matt.lamari at gmail.com> wrote:

>
> My main interest is in whether or not the library (that I know nothing
> about) can check dependencies quickly, or if dependency isn't
> specifically listed but merely a function of patch application voodoo.
>
> I am able to find dependANTS from the command line with:
>
> darcs obliterate --dry-run
>
>
> Is going to the library for such a task significantly faster?  Or does
> it still have to perform whatever mechanic that obliterate uses?
>
>
>
> _______________________________________________
> darcs-users mailing list
> darcs-users at darcs.net
> http://lists.osuosl.org/mailman/listinfo/darcs-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osuosl.org/pipermail/darcs-users/attachments/20120712/527e0bb9/attachment.html>