2014-07-15 10:35:28 +0200 <adimit> Welkin: you *can* install into your global ~/.cabal/bin, or symlink your sandboxes' binaries to ~/bin
2014-07-15 10:35:14 +0200 <MP2E> I agree, which is why I switched to nix and cabal2nix only a few weeks after trying cabal sandboxes :V
2014-07-15 10:34:48 +0200 <adimit> xpika: you could keep a shell open and alias cabal to cabal -w ghc_version.
2014-07-15 10:34:29 +0200 <Welkin> who is familiar with cabal sandboxes?
2014-07-15 10:29:23 +0200 <christiaanb> e.g.: cabal -w /opt/ghc/ghc-7.8.1/bin/ghc
2014-07-15 10:28:54 +0200 <christiaanb> xpika: cabal -w <path_to_ghc>
2014-07-15 10:28:40 +0200 <xpika> is there a way to cabal install with a specific ghc version?
2014-07-15 09:16:00 +0200 <Welkin> cabal always prints a lot of warnings and errors when installing packages
2014-07-15 09:14:34 +0200 <MP2E> with the new cabal
2014-07-15 09:14:27 +0200 <MP2E> this is just a guess, but perhaps .cabal/config from 1.14 is messing up the new one somehow? I heard something about having issues unless you force regenerate the config and redit that
2014-07-15 09:12:26 +0200 <bergmark> it can also be configured in .cabal/config
2014-07-15 09:08:14 +0200 <MP2E> and, better yet, when you update cabal again it'll just work
2014-07-15 09:07:59 +0200 <MP2E> you can actually place that in your .bashrc and you won't have to type it again, and the new cabal will overwrite the old one from now one
2014-07-15 09:07:36 +0200 <MP2E> so ~/.cabal/bin needs to be added to PATH
2014-07-15 09:07:21 +0200 <MP2E> They are in .cabal/bin the issue is is that your system doesn't automatically know to look in there
2014-07-15 09:07:06 +0200 <Welkin> but how? if the packages aren't in .cabal/bin ?
2014-07-15 09:05:52 +0200 <MP2E> try 'export PATH=~/.cabal/bin:$PATH' then try cabal --version
2014-07-15 09:04:02 +0200 <Welkin> there is nothing in .cabal/bin except for cabal itself
2014-07-15 09:03:08 +0200 <MP2E> $HOME/.cabal/bin also should precede everything else in your PATH, which is kinda important otherwise the global cabal could still overwrite it
2014-07-15 09:02:40 +0200 <supki> ok, do you have $HOME/.cabal/bin in PATH?
2014-07-15 09:02:16 +0200 <Welkin> cabal install cabal-install
2014-07-15 09:00:49 +0200 <Welkin> update cabal-install
2014-07-15 08:48:01 +0200 <Welkin> EvanR, do you know about ghc-pkg and cabal?
2014-07-15 08:41:42 +0200 <Welkin> how do I get ghc-pkg to recognize cabal-1.20.0 and use it instead of the old cabal-1.14.0?
2014-07-15 08:17:41 +0200 <Welkin> it uses the old version of cabal-install and ignores the new version
2014-07-15 08:17:29 +0200 <Welkin> what is up with cabal?
2014-07-15 06:22:07 +0200 <Algebr> How can I control some config in the config created by cabal sandbox init?
2014-07-15 05:50:14 +0200 <Algebr> cabal's config is really sensitive to layout.
2014-07-15 05:28:20 +0200 <dmj`> Algebr: I think you get ghci no matter what, I think cabal repl just changes your package database to that of the sandbox. In the case of no sandbox it's probably your user global package database
2014-07-15 05:26:47 +0200 <Algebr> If i do cabal repl in a non sandboxed directory, then I'm just getting plain vanilla ghci, right?
2014-07-15 02:12:01 +0200 <HorrendousRex> Hello! I'm getting the following error when I run "cabal tests" after adding a "test-suite tests" directive to my .cabal file: Warning: games.cabal: Unknown fields: default-extenstions (line 60)
2014-07-15 01:16:37 +0200 <bms1> I have a Cabal library which depends on a C library, and I want to be able to read the C headers (i.e., "include/") for the library. It looks like I'll probably need that directory to be specified manually? Is there a good way to do this?
2014-07-15 00:45:02 +0200 <dpwright> is that a cabal thing or a ghc thing?
2014-07-15 00:44:52 +0200 <dpwright> Is there any way to configure cabal to tweak the file extensions it will work with? I want to write some literate haskell/markdown files with extension ".hs.md" or ".lhs.md", but right now the extension has to be ".lhs"
2014-07-14 23:52:19 +0200 <Ivan_> I've been in cabal hell for a few hours now, just wondering if anyone had similar problems.