2014-04-23 02:03:03 +0200 <orion> Ok, here's a puzzle: I write a program which generates random bytes using a C library (which reads /dev/urandom). I generate 4 sets of random ByteStrings and print them to stdout in hex. If the code is compiled by hand (ghc), all four ByteStrings are different, as I would expect. If I use cabal, they are all the same.
2014-04-19 16:08:04 +0200 <geekosaur> there are mailing lists. most of what I'm aware of about it has been discussed on the glasgow-haskell-users and libraries lists. I am not subscribed to the cabal-dev list but I would expect detailed discussion of cabal trying to deal with the messes ghc hands it goes on there
2014-04-16 20:10:48 +0200 <pooya72> I had a question about member:HPC. How to you get it create the test coverage data (.tix .mix) from cabal-dev? I know you can do it when you build via GHC: ghc -fhpc Run.hs --make , but how do you do it from cabal-dev?
2014-04-16 20:02:39 +0200 <pooya72> I had a question about HPC. How to you get it create the test coverage data (.tix .mix) from cabal-dev? I know you can do it when you build via GHC: ghc -fhpc Run.hs --make , but how do you do it from cabal-dev?
2014-04-15 16:13:06 +0200 <joneshf-laptop> well, maybe i need to go try using cabal only again. the last time was a while ago and i wasn't using sandbox/cabal-dev
2014-04-11 02:14:41 +0200 <hpc> i am using cabal-dev, but the syntax is the same for just about everything
2014-04-07 22:27:16 +0200 <yitz> athan: 3. native sandboxes are strictly better than cabal-dev - you can choose cabal-dev style add-source by using --snapshot, or by default you get a source link that tracks changes in the remore sources.
2014-04-07 22:26:12 +0200 <yitz> athan: 2. cabal-dev isn't supported by anyone now
2014-04-07 22:26:01 +0200 <yitz> athan: 1. new cabal has critical features that you really want, and it doesn't work with cabal-dev.
2014-04-07 22:24:32 +0200 <yitz> pash: right, as dcoutts says, with my bootstrap procedure you only install new Cabal in that single cabal-dev sandbox, and then after that it's gone and everything still works fine.
2014-04-07 22:22:47 +0200 <athan> yitz: What's the major caveat of cabal-dev vs. cabal sandbox?
2014-04-07 22:22:17 +0200 <yitz> pash: so you bootstrap like this: 1. install a fresh HP. 2. immediately install cabal-dev, and nothing else. 3. use cabal-dev to install cabal-install from hackage. 4. put the new cabal binary in your path and kiss cabal-dev goodbye.
2014-04-07 22:18:37 +0200 <yitz> pash: i'm really not sure how well cabal-dev will work anymore. the code base isn't really supported.
2014-04-07 22:17:37 +0200 <pash> yitz: I know, but unfortunately I'm stuck with cabal-dev on this project for the moment ...
2014-04-07 22:17:14 +0200 <yitz> pash: use cabal's native sandboxes now. no reason to use cabal-dev anymore.
2014-04-07 22:16:44 +0200 <pash> How do I build a Tasty test executable with cabal-dev? I have things set up so I can run `cabal-dev test`, but I can't figure out how to compile tests/test.hs directly inside the cabal-dev sandbox ...
2014-04-06 06:13:44 +0200 <vu3rdd> cabal-dev .. can't parse --info output of ghc
2014-04-06 06:13:01 +0200 <vu3rdd> and then cabal-dev ghci but get this error: http://lpaste.net/102322
2014-04-06 06:12:51 +0200 <vu3rdd> and then did a cabal-dev install
2014-04-06 06:12:05 +0200 <vu3rdd> trying to follow along jekor's pandoc youtube video. Ran into a problem getting cabal-dev to work.
2014-04-05 00:30:42 +0200 <geekosaur> you can get much the same functionality from cabal-dev if you can't upgrade the Cabal library (which can break template haskell apparently) or cabal-install
2014-04-04 01:28:52 +0200 <srhb> Isn't cabal-dev basically replaced by the new sandboxing in cabal?
2014-04-04 01:26:49 +0200 <DarkFox> zipper: I also suggest using cabal-dev so you can use whatever versions you need in whereever you need any specific thing.
2014-04-03 21:56:29 +0200 <nh2> vozz_: replace `cabal-dev` by `cabal`
2014-04-03 21:53:30 +0200 <nh2> vozz_: can you try with plain cabal (or cabal sandboxes) instead of cabal-dev
2014-04-03 21:50:44 +0200 <nh2> vozz_: can you try `cabal-dev configure --enable-library-profiling --enable-executable-profiling && cabal build` and then see if it works with the executable in `dist/build/...`?
2014-04-03 21:46:06 +0200 <vozz_> cabal-dev install --enable-library-profiling --enable-executable-profiling works, but then running the executable with +RTS -p fails
2014-04-03 21:44:05 +0200 <vozz_> johnw: I did cabal-dev install --enable-library-profiling world and it installed things I don't need for this package, and failed on something... how do I ignore those?
2014-04-03 21:22:44 +0200 <johnw> cabal-dev install --enable-library-profiling world
2014-04-03 21:20:47 +0200 <vozz_> johnw: I tried doing that with cabal-dev but it doesnt seem to make a difference :(
2014-04-02 18:00:30 +0200 <MagneticDuck> question about automated haskell dev stuff: I'm trying to remember, what tools are there that do things like automatically adding elements to build-depends fields for cabal projects?
2014-03-31 21:48:15 +0200 <KatZilla> and got an error like this: cabal-dev: user error (cabal: Can't parse --info output of GHC
2014-03-31 21:48:12 +0200 <KatZilla> trying to run cabal-dev ghci
2014-03-31 21:38:04 +0200 <KatZilla> and got an error like this: cabal-dev: user error (cabal: Can't parse --info output of GHC
2014-03-31 21:37:51 +0200 <KatZilla> Trying to run cabal-dev ghci