2015-06-24 10:31:55 +0200 <barrucadu> http://coldwa.st/e/blog/2013-08-20-Cabal-sandbox.html#for-the-users-of-cabal-dev
2015-06-24 10:31:08 +0200 <barrucadu> m0rphism: Without looking into it, I assume cabal-dev's sandbox functionality predates cabal's
2015-06-24 10:30:47 +0200 <m0rphism> barrucadu: Is there some benefit for using regular cabal with sandboxes? I didn't knew this was possible. Where was the motivation for cabal-dev then?
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: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-23 02:19:59 +0200 <rofer> Is there a cabal-dev channel I could poke people in?
2015-05-30 12:53:50 +0200 <ph88> setup-Simple-Cabal- The pkg-config package 'fftw3f' version >=3.3 && <4 is required but it could not be found. do i need to install libfftw3-dev ?
2015-05-01 20:37:22 +0200 <slack1256> jo_os: http://dev.stephendiehl.com/hask/#cabal the easy way is explained there
2015-04-27 15:19:23 +0200 <benzrf> is there a notion of dev dependencies for cabal
2015-04-26 21:39:47 +0200 <dmj`> neuroserpens: when you specify the "O" it corresponds to Core transformations, the more transformations the more efficient your code can become, but the longer it will take to compile, so maybe make a flag "dev" "prod" etc. in your cabal file for those ghc-options
2015-04-18 17:53:35 +0200 <athan> You can also make your own isolated sandbox and use `cabal sandbox add-source ~/dev/foo` to add your functionality
2015-04-05 07:31:14 +0200 <Fylwind> but yeah I think the Cabal API docs are easier to read than the Cabal dev docs, but that's probably because I sort of already know where to look for things and don't need all the extra explanatory 'fluff'
2015-04-04 18:36:32 +0200 <noteventime> Geraldus: What happens if you set it to something explicit (the options here are: ghci, cabal-repl, cabal-dev, cabal-ghci)?
2015-04-03 16:15:07 +0200 <ph88> hey how can i make this work on windows? E:\dev\fuzzy>cabal install fft Resolving dependencies... Notice: installing into a sandbox located at E:\dev\fuzzy\.cabal-sandbox Downloading ix-shapable-0.1.0... Downloading storable-complex-0.2.2... Configuring storable-complex-0.2.2... Configuring ix-shapable-0.1.0... Building ix-shapable-0.1.0... Building storable-complex-0.2.2... Installed storable-complex-0.2.2 Installed ix-shapable-0.1
2015-03-15 20:27:22 +0100 <m0rphism> rui3: how are you installing your dependencies? I assume either cabal or cabal-dev?
2015-03-09 21:38:58 +0100 <gdoteof> i should probably clean the dev container at this point. in production i make the container on the fly with cabal install --only-dependencies
2015-02-28 18:41:05 +0100 <Cale> I don't know what it's called on arch, but on Mint, there's a libgtksourceview-3.0-dev package which you'd want to install before installing the cabal package for the Haskell binding.
2015-02-26 07:05:58 +0100 <pacak> zav: Because cabal-dev is no longer supported
2015-02-26 07:02:13 +0100 <zav> cabal sandbox vs cabal-dev anyone?
2015-02-13 18:48:58 +0100 <clintm> I just want to confirm that I'm on the right track with something. It's been a solid year since I've written anything and the dev environment seems to have changed. If I start from a bare machine with the latest stable ghc, and haskell/cabal from github, is it expected that if I want everything to work correctly, I sandbox everything else and symlink the executables? happy and alex come to mind.
2015-01-22 02:00:53 +0100 <meditans> benzrf: is here any cabal dev I could ask, here (I'm not posting this question in a mailing list because I suspect that the answer is no, and would like a quick check)
2015-01-17 23:40:13 +0100 <wolftune> Cale: the command I ran was cabal configure -f dev --enable-tests && cabal build -j5
2015-01-14 23:31:20 +0100 <luite> SrPx: you shouldn't install cabal 1.23 unles you want to do cabal dev, use the 1.22 branch
2015-01-12 18:32:12 +0100 <mpickering> cabal-dev is unmaintained now I think
2015-01-12 18:30:20 +0100 <developernotes> Has anyone run into a similar failure when attempting to install cabal-dev: http://pastie.org/9827794
2015-01-12 18:20:54 +0100 <developernotes> I am attempting to install cabal-dev with a fresh haskell install on OS X. I receive the following error (http://pastie.org/9827794) as it checks the dependencies. Any suggestions?
2015-01-10 05:42:05 +0100 <lisbeth> I need the fedora equivelent of zlib1g-dev in ubuntu, so that I can cabal install cabal-install
2015-01-02 21:37:19 +0100 <RedNifre> I haven't done any haskell dev in over a month, maybe it's been too long since I last ran cabal update so it needs too much memory now?
2014-12-29 16:26:09 +0100 <joroboro> cabal: There is no package named 'libghc-x11-dev'.
2014-12-29 14:59:03 +0100 <fizbin> So you see how my cabal-dev line there has those maximum version constraints on network and text...
2014-12-29 14:58:29 +0100 <fizbin> But the cabal file in the snap-server package will have the version constraints on text that snap-server uploaded with originally, so then cabal-dev will try to build and it'll say "wait, this version of text doesn't satisfy these constraints"
2014-12-29 14:57:26 +0100 <fizbin> Because what's happened is that the author of snap-server adjusted the version constraints when a newer version of text was published, but did so without pushing a new version of snap-server. So cabal-dev will pull the database, conclude "ah, snap-server can take the most recent version of text", install the most recent version, and then pull the snap-server package.
2014-12-29 14:55:29 +0100 <fizbin> So that means that you tell cabal-dev to do something like install "snap-server" and it'll go install a version of text and of network that it later yells at you about.
2014-12-29 14:54:37 +0100 <fizbin> The one weird thing about cabal-dev is that it doesn't compute dependencies properly for libraries that have had their descriptions updated through the hackage web interface without a new package being uploaded.