<br><br><div class="gmail_quote">On Tue, Apr 26, 2011 at 3:22 AM, Emil Axelsson <span dir="ltr"><<a href="mailto:emax@chalmers.se">emax@chalmers.se</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hello!<br>
<br>
I've had some of the usual problems with packages depending on multiple versions of another package. It seems the root of the hole problem was that I once attempted to run<br>
<br>
cabal install cabal-install<br>
<br>
This brought in a number of older packages (Cabal-1.8.0.6, containers-0.3.0.0, directory-1.0.1.2, filepath-1.1.0.4, process-1.0.1.5) to my local package DB, which led to inconsistencies when trying to install new packages.<br>
<br>
However, if I run<br>
<br>
cabal install cabal-install-0.10.2<br>
<br>
things work just fine. So the problem is that it wants to install an older version of cabal-install. A session demonstrating the problem is found below.<br>
<br>
Why doesn't cabal always install the latest packages?<br></blockquote><div><br></div><div>I consider this a bug but it's actually an intentional feature by the cabal developers. I explained it in the past here:</div>
<div><a href="http://osdir.com/ml/haskell-cafe@haskell.org/2010-09/msg00758.html">http://osdir.com/ml/haskell-cafe@haskell.org/2010-09/msg00758.html</a></div><div><br></div></div>