2014-10-15 10:38:07 +0200 <dmj`> merijn: I guess I'll just copy the same license in the module as in the cabal file, or maybe haddock will let me omit it, and still give me 100% coverage on that module
2014-10-15 10:31:39 +0200 <dmj`> jle`: yea they do, but can modules have a different license than the cabal file specifies? It would seem so, but that wouldn't make sense
2014-10-15 10:23:02 +0200 <jle`> dmj`: cabal files describe the library, not the individual modules...right?
2014-10-15 10:21:05 +0200 <dmj`> Fuuzetsu: module headers... is that really necessary :{ ... aren't the cabal files descriptive enough... ? Why do I need to put a license in every module
2014-10-15 10:18:19 +0200 <Fuuzetsu> dmj`: cabal is not taught about the flag directly, you'll have to use a pass-through; you might want to stick it into your global cabal config, I think there's haddock-options block now or something
2014-10-15 10:16:33 +0200 <jle`> dmj`: cabal haddock --haddock-options="--print-missing-docs"
2014-10-15 10:15:21 +0200 <dmj`> Fuuzetsu: oh, when I run cabal haddock --print-missing-docs it says its unrecognized, but haddock --print-missing-docs shows nothing
2014-10-15 04:58:40 +0200 <Javran1> hi, my emacs keeps telling me there is a "not in scope" error, but the source code is totally fine since it can be executed by runghc, this file is inside a cabal project so I guess something might be wrong there, how can I figure out what exactly is the problem?
2014-10-15 03:59:28 +0200 <Fuuzetsu> i.e. cabal build should just say OK
2014-10-15 03:59:10 +0200 <Fuuzetsu> is there a way to have cabal not produce any output? I just need a cabal file (because reasons) and I don't want to waste time compiling a dummy Main.hs
2014-10-15 03:57:59 +0200 <merijn> CrazyM4n: Alternatively, use cabal to build your own code, cabal should only pick one library version at a time
2014-10-15 03:53:34 +0200 <CrazyM4n> How do I uninstall cabal packages then?
2014-10-15 00:05:46 +0200 <latk> Is there some way to get a list of all the warnings generated when installing via cabal? Many of them seem to get lost in the compilation messages.
2014-10-15 00:04:02 +0200 <mgsloan> kadoban: Cabal 1.20 has the "exec" command to run binaries in the sandbox environment. I haven't tried that with ghc-mod, but I imagine it would work
2014-10-15 00:00:04 +0200 <kadoban> Does ghc-mod work with cabal sandboxes? I'm guessing probably not, huh?
2014-10-14 21:57:50 +0200 <luite> Fuuzetsu: yeah some packages like Cabal include some comment in their cabal file that shows how to generate some section
2014-10-14 21:51:28 +0200 <Fuuzetsu> is there a way to tell cabal to include all files under some directory in the tarball? We have hundreds of test files
2014-10-14 21:13:17 +0200 <steffen> I always run cabal build, even if I only want to know whether my code typechecks, is there a better way to use cabal and typecheck the project?
2014-10-14 19:27:53 +0200 <Fuuzetsu> NemesisD: enable Haddock (in your cabal file or else) and rebuild deps
2014-10-14 19:26:57 +0200 <NemesisD> how do you rebuild local haddocks for your dependencies in a cabal project
2014-10-14 18:18:38 +0200 <NemesisD> i've noticed that cabal sandboxes will prefer installed versions when new dependencies get added that require newer versions. is there a safe way to have cabal conservatively bump dependencies where necessary or do i need to blow away my sandbox
2014-10-14 15:55:34 +0200 <dcoutts_> Total_1mmersion: e.g. cabal install ./ -O2
2014-10-14 15:48:10 +0200 <Total_1mmersion> How do you tell cabal to compile with -O2? I've tried --PROG-options and --enable-optimizations
2014-10-14 13:35:43 +0200 <assia_t> I'm not even compiling anything, this is just `cabal update`...
2014-10-14 13:31:55 +0200 <assia_t> Has anyone tried to set-up a vagrant box with haskell? I'm trying to, but when I do `cabal update`, it runs out of memory (hehehe), consuming all 1048576bytes available
2014-10-14 09:57:03 +0200 <srenatus> "cabal: fromFlag NoFlag. Use fromFlagOrDefault" when trying to follow the stackage instructions, i.e. adding the snapshot's remote-repo line to .cabal/config. any hints?
2014-10-14 07:18:02 +0200 <Fuuzetsu> I'm just saying that if it's a choice between uploading a minor rev and changing the .cabal file on Hackage, you should upload
2014-10-14 07:15:57 +0200 <Fuuzetsu> editing .cabal files is evil, you should just upload minor rev with bounds fixed
2014-10-14 07:13:00 +0200 <carter> Cale: lets you edit .cabal files
2014-10-14 07:10:19 +0200 <merijn> thetrav: Conservative upper-bounds are good for avoiding future breakage, but may lead to cabal not finding an install plan if not all of the ecosystem has stabilised yet
2014-10-14 07:04:00 +0200 <thetrav> so one take-away though, is that cabal can install most packages, but not base?
2014-10-14 07:03:44 +0200 <Cale> thetrav: It's legit, just that .cabal file is slightly out of date
2014-10-14 07:02:05 +0200 <Cale> (Just saw the build-depends line in the suggested .cabal file)
2014-10-14 06:43:18 +0200 <michaelt> yyttr3: right, I think that's a feature of cabal install. if you first just do cabal configure, then every time you do `cabal build` it just rebuilds what it needs to.
2014-10-14 06:25:27 +0200 <yyttr3> michaelt: If you don't mind also, how do I rebuild a project with cabal? When I call cabal install -j again it creates new folders, not update them