Given that I have the dependant packages already installed when I do
$ cabal install --dry-run --global buildwrapper Resolving dependencies... In
order, the following would be installed: mtl-2.1.1 (new version) aeson-0.6.0.2
(reinstall) changes: mtl-2.0.1.0 - 2.1.1 parsec-3.1.2 (reinstall)
Have solved the issue with help from JP Moresmau.
Used the command
cabal install --dry-run --verbose=3 --global build wrapper
And this gave enough detailed info to enable me to remove the conflict and
resolve the issue.
Thanks goes to JP !
On Wednesday, 9 May 2012 at 09:55, Graham Berks
I understand that this may have been addressed before on this list in some
form, so I'll be brief:
Had problem with deprecated package, was told my only option was to wipe my
Haskell install and start over. Is this true and if so, doesn't this mean
that Cabal (or the package management system
Not what you asked for, but..
Although the documentation looks somewhat cryptic, and I have not use it at
all, a nix + cabal option seems to be in the works.
Search google for nix haskell. I am guessing that their Hydra continuous
build system which is built on top of nix also could do wonders
On Fri, Dec 9, 2011 at 5:20 AM, Kevin Jardine kevinjard...@gmail.com wrote:
I understand that this may have been addressed before on this list in some
form, so I'll be brief:
Had problem with deprecated package, was told my only option was to wipe my
Haskell install and start over. Is this
On Fri, Dec 9, 2011 at 06:20, Kevin Jardine kevinjard...@gmail.com wrote:
Had problem with deprecated package, was told my only option was to wipe
my Haskell install and start over. Is this true and if so, doesn't this
mean that Cabal (or the package management system that it is a part of) is
