March 2014 - cabal-devel

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