<br><br><div class="gmail_quote">On Mon, Apr 12, 2010 at 4:00 AM, Duncan Coutts <span dir="ltr"><<a href="mailto:duncan.coutts@googlemail.com">duncan.coutts@googlemail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Sun, 2010-04-11 at 14:28 -0700, Jason Dagit wrote:<br>
<br>
> I've noticed another type of diamond dependency problem. Suppose I<br>
> build and install Foo today and it depends on Bar 2.0.0. In a week, I<br>
> install Bar 2.0.1. Next I installed Baz that also depends on Bar, and<br>
> it gets Bar 2.0.1. When I install a package that depends on Foo, Baz,<br>
> and possibly Bar, then cabal won't be able to figure out proper<br>
> dependencies because Foo needs one version of Bar and Baz needs a<br>
> different version.<br>
<br>
</div>That's exactly the problem that cabal-install solves. It will rebuild<br>
one or the other of Foo and Baz so that the dependency on Bar is<br>
consistent.<br></blockquote><div><br>Weird. This has not been my experience.<br><br>Jason<br></div></div>