Mmm, my email was indeed very unclear about my question.<div><div><br></div><div>A very simple example: suppose a development team is working on a program. This program consist of modules A and B. Each module has it's own Darcs repository.</div>
<div><br></div><div>Module A requires B. When a new developer wants to get the source code, he does a "darcs get server://program/A", which gives him only the latest version of A. So he manually needs to do "darcs get server://program/B" (that B is required is usually discovered after a compilation error, talking to other developers to find out what the dependencies are, or by reading the cabal file). Furthermore it is unclear which version of A required which version of B (so you can't really roll back to old versions).</div>
<div><br></div><div>Now assume you don't have 2 modules but dozens...</div><div><br></div><div>To me, any version control system should be able to track dependencies between repositories. Something similar like Cabal's dependency system.</div>
<div><br></div><div>So my question is really, how do you solve the dependency tracking between several Darcs repositories? </div><div><br></div><div>(maybe I should email this to the darcs mailing list...)</div><div><br></div>
<div><div><div><div class="gmail_quote">On Sat, Mar 28, 2009 at 4:54 AM, Simon Michael <span dir="ltr"><<a href="mailto:simon@joyful.com">simon@joyful.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
I assume cabal install darcs isn't what you're looking for.. can you give a real-world example ?<br>
<br>
_______________________________________________<br>
Haskell-Cafe mailing list<br>
<a href="mailto:Haskell-Cafe@haskell.org" target="_blank">Haskell-Cafe@haskell.org</a><br>
<a href="http://www.haskell.org/mailman/listinfo/haskell-cafe" target="_blank">http://www.haskell.org/mailman/listinfo/haskell-cafe</a><br>
</blockquote></div><br></div></div></div></div>