2016-12-28 16:09:56 +0100 <ertes> cabal-install has the delay, too: real 0.306 user 0.278 krnl 0.023 cpu% 98% mem 34m cabal --help > /dev/null
2016-10-06 08:53:33 +0200 <hvr> ...and stack actually accelerated cabal dev ;-)
2016-09-22 18:44:11 +0200 <maerwald> ertesx: I know one or two packages that really have cabal hell... and the dev uses stack ;P coincidence? No.
2016-09-06 19:50:40 +0200 <maerwald> cabal is not a tool for sharing dev environments
2016-06-17 00:21:38 +0200 <ClaudiusMaximus> MetalOn: not sure what the quickest fix would be - possibly wiping installed packages (cabal sandbox delete; harder if not using sandboxes), adding library-profiling: True to ~/.cabal/config (first thing i do when setting up a new dev system...) and retry, making sure to use sandboxes (cabal sandbox init)
2016-06-02 15:24:46 +0200 <dcoutts> idev: typically you don't want to hard code -Werror into .cabal files (or if you do, you have to guard it with a "dev" flag or similar)
2016-05-16 04:37:38 +0200 <tomleb> remote: cabal: No sandbox exists at /home/tomleb/dev/web/portfolio/.cabal-sandbox
2016-05-02 13:08:33 +0200 <bloomyGloom> i'll sandbox that cabal hell into a dev's corner when i'm done with this.
2016-04-27 01:25:02 +0200 <hpc> i know in cabal-dev you can use cabal-dev add-source /path/to/dir
2016-04-18 23:26:13 +0200 <text_builder> but then it is not "cabal configure --dev"
2016-03-27 21:08:23 +0200 <ertesx> i believe that's what cabal-dev did essentially
2016-03-27 20:54:57 +0200 <Hegg> hjulle: I don't think 1.16 has sandboxes, and the admin for the computer won't install cabal-dev =/
2016-02-22 06:13:46 +0100 <Clint> fortress_: depends how you install things.. perhaps `cabal install text` or `apt-get install libghc-text-dev`
2016-01-14 12:53:44 +0100 <danilo2> Hello guys! What is the convention in Haskell / GHC to "include" CPP Header files with macros? Lets say create a library installable by cabal and it contain CPP header that I want to include in other files, how can I import or handle it? Right now I'm using the #include pragma with full path and it works, but this is for dev purpose only
2016-01-14 03:44:44 +0100 <koz_> I wrote my .cabal based on what cabal configure gave me, and this: http://dev.stephendiehl.com/hask/#cabal
2016-01-02 17:29:36 +0100 <bergmark> cabal-dev still had a place until stack came out since it had more hacky behavior than cabal sandboxes allowed :)
2016-01-02 17:27:30 +0100 <parsnip> oh, i was watching Pandoc Part 2 on Code Deconstructed - Episode 2 - YouTube.html https://www.youtube.com/watch?v=nCwG9ijQMuQ, and he suggested cabal-dev to work with pandoc interactively.
2016-01-02 17:27:02 +0100 <bergmark> our cabal-dev fork works at least up to 7.8, but we don't use cabal-dev anymore either: https://github.com/silkapp/cabal-dev
2016-01-02 17:26:10 +0100 <geekosaur> is cabal-dev still maintained?
2016-01-02 17:24:23 +0100 <parsnip> hmm, i deleted .ghc and .cabal, and `cabal install cabal-dev` is still now working.
2016-01-02 07:58:36 +0100 <parsnip> hmm, so cabal-dev can be used to for example run pandoc in ghci?
2015-12-12 08:57:42 +0100 <pdxleif> bitemyapp: Yeah - there's a "CI" flag passed on travis to turn on fatal warnings: https://github.com/idris-lang/Idris-dev/blob/master/idris.cabal#L1019
2015-11-19 20:44:16 +0100 <bergmark> long live cabal-dev
2015-11-17 23:39:55 +0100 <ttt_fff> this might be OT (but is for my haskell dev). So I'm using (1) vim, (2) cabal repl, (3) tmux, and (4) now -- nixos. My old setup was (1) put a "cabal repl" inside a named tmux (2) vim can then pipe commands to cabal repl by using tmux. Recently, I switched from ubuntu to nixos. Unfortunately, nix-shell appears to screw up my tmux where two tmuxes can only talk to each other if in the same nix-shell. Has a
2015-11-06 17:14:12 +0100 <quicksilver> suppi: http://dev.stephendiehl.com/hask/#cabal
2015-11-04 15:15:21 +0100 <dcoutts> merijn: current cabal-install doesn't deal with the implicit dependencies of Setup.hs scripts. (Though the new dev branch does)
2015-10-14 13:28:51 +0200 <hpc> i remember cabal-dev and then manually copy was something i liked to do for crazy stuff like mueval
2015-10-04 17:45:10 +0200 <mreh> Welkin, even using cabal-dev?
2015-09-27 07:04:59 +0200 <hftf> I'm trying to set up a dev env for pandoc alongside a stable version. Last time I was able to name the dev build as pandoc-1.15 to not clash with the pandoc name, but I can't remember how. Is there a cabal option to do this?
2015-09-21 14:07:57 +0200 <xyh> kaidelong: every time you dev a package, you just add its '.cabal-sandbox/bin' to your 'PATH' ??
2015-09-10 11:38:21 +0200 <bergmark> i'm still using our old cabal-dev sandbox setup for most things, it puts all sandboxes in ~/.cabal-dev so i don't accidentally delete them if i delete a checkout
2015-08-21 19:48:57 +0200 <codedmart> I have this in a cabal file https://github.com/AtnNn/haskell-rethinkdb/blob/f700133a4c2935389e1dd69ef887ae5f84cbe58a/rethinkdb… under an if flag(dev). Travis cabal check is failing on 7.10 with `'ghc-prof-options: -fprof-auto' is fine during development…`
2015-08-20 08:30:59 +0200 <xelxebar> I don't really know nix all that well, and while the problem persists, I can't really use my dev tools. So, this is really silly, but I wrote a cabal wrapper to manage a "cabal store" of individually sandboxed packages.
2015-08-11 10:33:46 +0200 <bennofs> + some scripting so I can load any haskell project with a cabal file in 3 commands (and it fetches most haskell lib deps from binary cache, so it's fast (but only for GHC 7.10)): themplate init <project> haskell-nix; cd <project>; dev-shell :)
2015-08-06 01:00:54 +0200 <drewbert> We just need to get stack support into ghc-mod, flymake, leksah, and all the other dev tools that rely on a traditional cabal setup.