Hi Greg,<br><br><div class="gmail_quote">On Mon, Nov 19, 2012 at 1:25 PM, Gregory Guthrie <span dir="ltr"><<a href="mailto:guthrie@mum.edu" target="_blank">guthrie@mum.edu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I follow the Cabal-messes threads with some interest, since that is the hardest area for me since starting to use Haskell. Probably 40-60% of all package install fail for some mysterious reason, with threats that trying to fix them will break more things, which generally is true. :-)<br>
</blockquote><div><br></div><div>We're working on it. Be brave, things are going to get better!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I am not exert in the area, but I wonder how /why/ this is different than other package managers, like apt in Linux, I have never had any problems with it, and I would think that their dependencies are of at least similar complexities.<br>
</blockquote><div><br></div><div>The Linux package managers solve a different problems. They let you install a set of packages that have been manually curated and are know to work together (i.e. all version dependencies are fixed) while cabal does version resolution on packages that might not ever have been tried together. If you install Haskell packages via your distro's package manager I assume they will always install cleanly. The problem is that people want the latest bleeding edge of packages, which haven't made it into the distros yet, and hence they get to experience some of the pains associated with being on the bleeding edge. Being on Windows also makes things harder, as most developers don't have a Windows box to test their stuff on.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">In any case; Trying to do a cabal update" I was told to try to update "cabal-install", which I think means actually updating cabal (since I actually run installs via cabal install...), but that fails with this message below, and I don't know how to proceed.<br>
</blockquote><div><br></div><div>cabal-install is the package that includes the "cabal" executable. Cabal (with a capital C) is the library that cabal-install uses. The naming is unfortunate but hard to change at this point. To update cabal-install you do:</div>
<div><br></div><div>$ cabal update && cabal install cabal-install</div><div><br></div><div>Make sure that the place that the "cabal" binary gets installed into (which is printed at the end of the install) is on your PATH.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Linking C:\Users\guthrie\AppData\Local\Temp\Cabal-1.16.0.3-13880\Cabal-1.16.0.3\dist\setup\setup.exe ...<br>
Configuring Cabal-1.16.0.3...<br>
Warning: This package indirectly depends on multiple versions of the same<br>
package. This is highly likely to cause a compile failure.<br></blockquote><div><br></div><div>This is a sure sign that things are not going to work well. Could you include the output of</div><div><br></div><div>cabal install -v cabal-install</div>
<div><br></div><div>please. The output here is not enough to tell me what's going on. Please also include the output of</div><div><br></div><div>cabal --version</div><div>ghc --version</div><div><br></div><div>Are you using the Haskell Platform, if so, which version?</div>
<div><br></div><div>-- Johan</div><div><br></div></div>