- cabal-devel - Haskell.org

Github issues database really needs a cleanup
by Bryan O'Sullivan 16 Mar '14

16 Mar '14

There are literally hundreds of issues in there that I imported during the migration from trac that have never been touched since. Having the issue tracker be a graveyard of ancient junk that will never be touched does not strike me as a healthy state of affairs. Would anyone mind if I were to triage some of the old stuff and kill it off?

3 2

cabal doesn't explore the none manual flags very well
by Carter Schonwald 12 Mar '14

12 Mar '14

Hey all, i'm repeatedly seeing many examples where a Manual : False flag is used to encode an "OR" in the cabal configuration, and where cabal "gives up" on finding the "right" build plan i know it can find if it has to flip the flag in a dependency its building... Is this a known issue? how can i mitigate it?

3 4

Cabal-1.18.1.3 and cabal-install-1.18.0.3 releases made
by Johan Tibell 07 Mar '14

07 Mar '14

Hi, I've just made a release of Cabal/cabal-install, for the benefit of GHC 7.8. People have in the past expressed a desire for having prebuilt binaries of cabal-install. I'm happy to upload such binaries if people send them to me. Please specify for which arch/OS the binary is built. -- Johan

2 1

Gearing up for 1.20
by Johan Tibell 05 Mar '14

05 Mar '14

Hi, I'd like to get 1.20 out by the end of the month. There's enough interesting stuff in there to be worth making a release. Here are the current open issues for the 1.20 milestone: https://github.com/haskell/cabal/issues?milestone=21 These are mostly feature requests so we could technically do without any of them, but it would be nice to knock some off if people have some free weekend hacking time. Thoughts? -- Johan

1 0

The 1.18 branch is reaching end-of-life
by Johan Tibell 04 Mar '14

04 Mar '14

Hi, With the 1.18 releases for GHC 7.8 out of the way, I'm going to retire the 1.18 branch* so please don't push any more commits to it. * Except if there are any late minute fixes *required* for GHC 7.8 to work well. -- Johan

1 0

Haddock fails with "Module defined in multiple files"
by Mateusz Kowalczyk 04 Mar '14

04 Mar '14

Hi, We just got a bug report over at Haddock Trac[1]. What's not mentioned is that it works fine for the user on GHC 7.6.3 with Haddock 2.13.1. I can't think of any Haddock changes that could have potentially caused the reported breakage. This e-mail is to ask whether any Cabal(-install) devs can think of anything that might have changed on your end of things that could cause this before we go off chasing a bug in the wrong project. I don't follow the changes in cabal (even though I should) so it might be something really obvious that changed recently that we aren't aware of. Thanks [1]: http://trac.haskell.org/haddock/ticket/284 -- Mateusz K.

2 2

check-pvp
by Henning Thielemann 01 Mar '14

01 Mar '14

Following Mikhail Glushenkov's advice I have prepared a separate tool that checks PVP compliance of imports as proposed in: https://github.com/haskell/cabal/issues/1703 There remain some problems: * How can I exclude automatically generated modules like Path_*.hs from the check? * How can I access modules that are preprocessed? HSC processed modules are stored in dist/build, but CPP processed modules are not stored anywhere. * How shall I cope with condition flags? Currently I use flattenPackageDescription. Alternatively I might only check the modules that are part of the current configuration. But I may miss many modules this way. I might perform checks on all possible configurations. * Can you give me advice on what I shall write to stdout and what to stderr? The purpose of the program is to generate a list of warnings. Shall they be written to stderr because they are warnings or shall they be written to stdout because they are the intended output of the program? * Regarding levels of verbosity: How silent shall silent be? Shall the test results be emitted in silent mode or only in normal verbosity mode?

3 17

Cabal File Pretty Printer
by Daniel Trstenjak 01 Mar '14

01 Mar '14

Hi all, the current cabal file pretty printer creates output in the form: ... extra-source-files: README.md tests/inputFiles/original.cabal tests/inputFiles/setup-config tests/goldenFiles/*.cabal tests/outputFiles/.gitignore library build-depends: base >=3 && <5, cmdargs >=0.10.5 && <0.11, lens >=4.0.1 && <4.1, strict >=0.3.2 && <0.4, Cabal >=1.18.0 && <1.19 exposed-modules: CabalBounds.Args CabalBounds.Main ... other-modules: Paths_cabal_bounds CabalBounds.Bound CabalBounds.Targets CabalBounds.Dependencies CabalBounds.Drop CabalBounds.Update CabalBounds.Lenses ... Would a patch be accepted that creates output that is more diff friendly? Something like: extra-source-files: README.md tests/inputFiles/original.cabal tests/inputFiles/setup-config library build-depends: base >=3 && <5, cmdargs >=0.10.5 && <0.11, lens >=4.0.1 && <4.1, exposed-modules: CabalBounds.Args CabalBounds.Main ... other-modules: Paths_cabal_bounds CabalBounds.Bound CabalBounds.Targets ... Or perhaps: extra-source-files: README.md tests/inputFiles/original.cabal tests/inputFiles/setup-config library build-depends: base >=3 && <5, cmdargs >=0.10.5 && <0.11, lens >=4.0.1 && <4.1, exposed-modules: CabalBounds.Args CabalBounds.Main ... other-modules: Paths_cabal_bounds CabalBounds.Bound CabalBounds.Targets ... I think that I might prefer the second one. Greetings, Daniel

8 11

Cabal-1.18.1.3 and cabal-install-1.18.0.3 RCs
by Johan Tibell 01 Mar '14

01 Mar '14

Hi all, I've uploaded release candidates for Cabal-1.18.1.3 (to be shipped with GHC 7.8) and cabal-install-1.18.0.3. You can install the RCs like so: cabal install http://johantibell.com/files/Cabal-1.18.1.3-rc.tar.gz http://johantibell.com/files/cabal-install-1.18.0.3-rc.tar.gz It's especially important that Cabal-1.18.1.3 gets some testing on OS X using GHC 7.8, as there's a change in how linking is done (see https://github.com/haskell/cabal/issues/1660) These RCs correspond to commit d310d87c2c445f52987169a2ce4da03c14070918 on the 1.18 branch in the cabal repo [1]. Note that both Cabal and cabal-install are released from the same repo. If you want to check which commits are new since last release run: git log Cabal-v1.18.1.2.. -- Cabal/ git log cabal-install-v1.18.0.2 -- cabal-install/ -- Johan 1. https://github.com/haskell/cabal

1 0

Uploading to Hackage Problems
by Dominic Steinitz 24 Feb '14

24 Feb '14

I am trying to upload a new version of a package but I get a page saying “no authorisation provided” (the url is http://hackage.haskell.org/packages/candidates/) and I could find no way of logging in. The page http://hackage.haskell.org/packages/upload merely has a “choose file” button and an “upload package” button. Dominic Steinitz dominic(a)steinitz.org http://idontgetoutmuch.wordpress.com

3 7