2015-06-24 10:26:17 +0200 <m0rphism> IIRC to use cabal-dev I first cleaned the previous package conflict be removing the packages installed via regular cabal by removing ~/.cabal and then only used plain cabal to install cabal-dev.
2015-06-24 10:25:35 +0200 <barrucadu> There's also sandboxes with regular cabal
2015-06-24 10:23:46 +0200 <m0rphism> haskell783: nix and stackage take a bit time to get into, cabal-dev behaves the same as cabal, but by default installs everything into $(pwd)/cabal-dev
2015-06-24 10:22:43 +0200 <m0rphism> haskell783: Instead the current practices seem to use either cabal-dev, which builds each project including its dependencies in a sandbox,
2015-06-24 10:21:26 +0200 <m0rphism> haskell783: AFAIK plain cabal currently doesn't serve well for installing multiple projects, as they might depend on different versions of the same library, which isn't handled well at the moment.
2015-06-24 10:03:39 +0200 <haskell783> My current version of ByteString is and doing cabal update bytestring --reinstall gives me a strange error "(global constraint requires installed instance)". What can be done to fix this.
2015-06-24 05:29:46 +0200 <Cale> http://hackage.haskell.org/package/cabal-install-
2015-06-24 05:29:17 +0200 <atgnag__> Now I need cabal.
2015-06-24 02:23:09 +0200 <Luke> bitemyapp: any word on why cabal doesn't support extra-include-dirs in the cabal file?
2015-06-23 23:14:51 +0200 <P4Titan> Hello all, could someone help me with some cabal work? I try to do cabal install --only-dependencies and it says there are unresolved dependencies: base==, detexify-hs-backend => base>=4.7 && <4.8. I cleared the ~/.ghc and ~/.cabal dirs, reinstalled cabal, but still it is not working
2015-06-23 22:54:36 +0200 <joco42> hamishmack: In the picture I would like to look up the definition of 'mainWidget' which is in the reflex-dom library which is installed into a sandbox (because it cannot be installed globally due to cabal hell)
2015-06-23 22:50:49 +0200 <joco42> hamishmack: In Leksah, If I open a cabal package that uses libraries installed into a shared sandbox then how can I include those libraries into the metadata indexed by Leksah?
2015-06-23 22:15:13 +0200 <tdammers> ooooh, looks like I need to force Cabal to >=1.22
2015-06-23 22:11:44 +0200 <tdammers> basically I'm trying to use cabal-test-quickcheck with the detailed-0.9 test interface
2015-06-23 22:10:43 +0200 <lpaste_> tdammers pasted “cabal error” at http://lpaste.net/135063
2015-06-23 22:10:33 +0200 <kqr> srhb, i'm not running cabal install, i'm running cabal build :)
2015-06-23 22:08:47 +0200 <hexagoxel> Fernandos: that looks like https://github.com/quchen/cabal-install-bin/blob/master/cabal-install-bin
2015-06-23 22:07:14 +0200 <Fernandos> now I'm using this snippet: cd $(mktemp -d -t cabal-XXXX); cabal sandbox init && cabal install --disable-documentation --disable-library-profiling --disable-shared --disable-executable-dynamic --bindir="$HOME/.cabal/bin" --datadir="$HOME/.cabal/share" -allow-newer <package-name-here>
2015-06-23 22:05:48 +0200 <srhb> kqr: Shouldn't that be autofetched in the install step after cabal configure?
2015-06-23 22:04:40 +0200 <kqr> I forgot to cabal install --only-dependencies
2015-06-23 22:04:05 +0200 <Fernandos> hahah that error sounds funny sorry :) I had to fight a lot with cabal too..
2015-06-23 22:03:55 +0200 <kqr> just not if I have it in my cabal file?
2015-06-23 22:03:51 +0200 <kqr> but if I install with "cabal install random-shuffle" it works
2015-06-23 22:03:16 +0200 <kqr> bergmark, for me cabal-install complains that "cabal: At least the following dependencies are missing: random-shuffle -any"
2015-06-23 22:00:44 +0200 <srhb> kqr: It works fine, cabal unpack it and just remove the constraint on base
2015-06-23 21:58:17 +0200 <kqr> and cabal doesn't seem to want to know about it
2015-06-23 20:17:18 +0200 <kadoban> osa1: I think it does. IIRC ghc-mod is broken with too-new cabal and ghc 7.8?
2015-06-23 20:16:10 +0200 <osa1> is ghc 7.8 not working with cabal 1.22?
2015-06-23 20:14:04 +0200 <Welkin> of course, with carefully crafted cabal.config constraints
2015-06-23 20:10:16 +0200 <maerwald> the problem with haskell is... it's almost impossible to use without cabal sandboxes... so if you want to use your package manager to install haskell stuff, you end up with unresolvable dependencies, unless your package manager has it's own way of sandboxes (e.g. nixos)
2015-06-23 20:04:39 +0200 <kadoban> maerwald: I do the same except I just go one step farther and avoid the GHC and cabal from the OS package manager too.
2015-06-23 20:02:56 +0200 <maerwald> because the haskell dependency constraints are so tight that it confuses a lot of package managers (including cabal)
2015-06-23 20:02:11 +0200 <kadoban> Gurkenglas: If you end up going that way, this is how I install GHC/cabal: https://gist.github.com/ion1/2815423
2015-06-23 20:01:03 +0200 <kadoban> maerwald: Is there any OS that has good haskell out of the box? I'd install just GHC and cabal manually from the binaries and then use cabal sandboxes.
2015-06-23 19:48:47 +0200 <Welkin> Gurkenglas: I have been using it now for over a year as well and just last week I had a nightmare situation with ghc and cabal