gistfile1.txt

19:11:21 dminuoso | +1
19:11:30 dminuoso | Or just `cabal install` at all
19:12:09 dminuoso | backleet: just delete the entirety of your ~/.cabal I say
19:12:19 dminuoso | That's easier than going through the gory details
19:12:30 dminuoso | Or should ~/.ghc deleted be too?
19:12:35 dminuoso | Im not sure. Delete both for good measure. :-)
19:12:45    Solid | :D
19:13:15 dminuoso | backleet: ^- I'm not kidding by the way. There's probably a more precise way, but if you want the simple "give me a damn command solution", that's it.
19:13:23    Solid | backleet: if your distro doesn't package xmonad or you want to install a newer version, I'd recommend installing via a stack project as per the install
                  | instructions ( https://github.com/xmonad/xmonad/blob/master/INSTALL.md )
19:15:09 dminuoso | backleet: Normally `cabal` is for building projects, so each project would have a `foo.cabal` file declaring its build dependencies. And then you just run
                  | `cabal build`, it would automatically grab dependencies for this project in isolation behind the scenes (avoiding dependency hell), there's no way to
                  | "install/uninstall" dependencies anymore
19:16:46      --> | backleet (~mm@116.251.216.46) has joined #xmonad
19:16:58 backleet | I got disconnected dminuoso, did you write anything?
19:17:02 dminuoso | xmonad is an odd candidate, because it requires this full compilation process. The proper way to fit this together is to have a my-xmonad project with a
                  | my-xmonad.cabal file, which declares the dependencies on xmonad, utf8-string and whatever else you want. This approach can be done, but it takes some minor
                  | additional work to play nice