2014-09-13 19:48:50 +0200 <msafi> dmj`, I don't have a ~/.cabal/bin
2014-09-13 19:48:15 +0200 <geekosaur> that controls where things get installed, if you dont have one then cabal creates one with the default OS X paths but if you have one already then you need to check it to see where stuff will go
2014-09-13 19:47:46 +0200 <geekosaur> hm. did you have a ~/.cabal/config already?
2014-09-13 19:47:42 +0200 <dmj`> msafi: check if its in ~/.cabal/bin
2014-09-13 19:47:17 +0200 <msafi> geekosaur: I did cabal install ghc-mod. ~/Library/Haskell/bin is still empty.
2014-09-13 19:44:27 +0200 <geekosaur> ghc-mod is a package, "cabal install ghc-mod" should work. http://hackage.haskell.org/package/ghc-mod
2014-09-13 19:36:10 +0200 <geekosaur> something installed with "cabal install" is a user package
2014-09-13 19:01:27 +0200 <dmj`> dfarm: when you invoke emacs, do so by using cabal exec emacs. This should update your package db
2014-09-13 18:59:56 +0200 <dfarm> Hey all, quick cabal + emacs question. I'm trying to get M-x compile to work in my cabal sandboxed project but it's not aware of the sandbox. Any quick way to get this working?
2014-09-13 04:33:03 +0200 <yyttr3> carter: "brew install wxmac --devel ", then "cabal install wx cabal-macosx"
2014-09-13 03:46:33 +0200 <bitemyapp> Fuuzetsu: if a patch doesn't manifest around the time they start talking about a release, I'll do it myself. I'd rather not as I don't know Cabal or cabal-install internals very well.
2014-09-13 03:45:45 +0200 <bitemyapp> Forkk: I am telling Fuuzetsu about this because cabal-install is getting a feature based on his blog post.
2014-09-13 03:42:22 +0200 <bitemyapp> Fuuzetsu: I put a bug in the ear of the Cabal elves and hopefully a `cabal upload --haddock` will manifest.
2014-09-13 03:40:26 +0200 <Fuuzetsu> bitemyapp: I'm not aware of this Cabal haddocks incident you're talking about
2014-09-13 03:40:01 +0200 <bitemyapp> Fuuzetsu: you saw how impatient I got with the Cabal haddocks nonsense. That was bad UX and documentation too.
2014-09-13 03:21:05 +0200 <solatis> hexagoxel: Fuuzetsu suggested the big hammer of Nix to me instead of trying to work around cabal
2014-09-13 03:20:45 +0200 <solatis> hexagoxel: i'm having cabal package conflict hell
2014-09-13 02:44:58 +0200 <merijn> kadoban: Try building with -v3 for cabal and see where it dies, if it's on some dependency, try installing it manually and if that crashes GHC somehow (like for me) try installing pandoc without profiling
2014-09-13 02:42:23 +0200 <trap_exit> cabal install work-first-time-damnit
2014-09-13 02:42:15 +0200 <hpc> cabal install quality
2014-09-13 02:40:44 +0200 <trap_exit> kadoban: and cabal reported "I can't download from hackage" as "hey user, something went wrong"
2014-09-13 02:37:45 +0200 <MichaelBurge> solastic: Do a 'cabal sandbox init' in the directory you're working in, and then 'cabal install'. Oftentimes, if you install packages one-by-one Cabal can get stuck, but if you start fresh and give it the whole picture it can figure out the dependencies
2014-09-13 02:27:10 +0200 <lpaste_> solatis pasted “Cabal dependency conflics” at http://lpaste.net/110961
2014-09-13 02:08:15 +0200 <nshepperd> build in sandbox, cabal install everythng at once
2014-09-13 02:05:32 +0200 <solatis> so, what's the best way to resolve cabal package conflicts? shoot myself?
2014-09-12 21:48:57 +0200 <nyuszika7h> I updated cabal-install to 1.20 with itself because 1.16 didn't have a sandbox and HP wouldn't build
2014-09-12 21:48:19 +0200 <napping> nyuszika7h: a recent cabal will pick a decent default -j
2014-09-12 21:46:43 +0200 <nyuszika7h> http://ivanmiljenovic.wordpress.com/2010/03/15/repeat-after-me-cabal-is-not-a-package-manager/
2014-09-12 21:43:40 +0200 <merijn> mzero: Sure, but if you're gonna build stuff yourself does the platform really offer all that much over just installing GHC+cabal and installing stuff by hand?
2014-09-12 21:41:34 +0200 <merijn> nyuszika7h: So, install that, download and install cabal-install and call it a day?
2014-09-12 21:41:29 +0200 <nyuszika7h> I think the problem is I didn't install the whole platform package in the first place, only ghc, cabal-install, haddock, hscolour, etc.
2014-09-12 21:37:53 +0200 <nyuszika7h> I didn't install the whole platform, only ghc, cabal, hscolour, haddock, and other necessary things
2014-09-12 21:34:48 +0200 <mzero> Cabal won't tell you about what a module exports
2014-09-12 21:34:24 +0200 <geekosaur> and/or the Cabal module
2014-09-12 21:32:38 +0200 <joshkirklin> not even to inspect the modules available in the current cabal environment?