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

[Ganesh Sittampalam]

Hi,

If you just want to know what patches transitively depend on a single
given patch X, obliterate --dry-run is probably good enough.

If you want just the direct dependencies, or you want to do it for lots
of patches at once, doing it in code with the library would be a better
choice. There isn't a single function that will do it, but it shouldn't
be particularly complicated. I'd be hapy to outline or prototype what to
do if you can give details of exactly what info you're looking for.

Cheers,

Ganesh

On 12/07/2012 20:58, Matt Lamari wrote:
> 
> 
> 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
> 
> _______________________________________________
> darcs-users mailing list
> darcs-users at darcs.net
> http://lists.osuosl.org/mailman/listinfo/darcs-users
>