December 2007 - cabal-devel

[Hackage] #191: Hackage should check for common QA problems in ghc-options
by Hackage 11 Feb '08

11 Feb '08

#191: Hackage should check for common QA problems in ghc-options --------------------------+------------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.1 Platform: Linux | --------------------------+------------------------------------------------- Simple test that many packages have is dodgy ghc-options, or options that would be suitable for development but not release. It should be easy to check for these. Suggestions: {{{ghc-options: -Wall -Werror}}} is a very bad combination. It means the package will break silently as soon as the next version of ghc adds a new warning, which generally does happen every major release. {{{ghc-options: -fasm}}} is unnecessary and breaks on all arches except for x86, x86-64 and ppc. {{{ghc-options: -O}}} is unnecessary since Cabal does that itself and it prevents people from configuring with the {{{--disable-optimization}}} flag. {{{ghc-options: -O2}}} may be necessary in some circumstances but people should not use it routinely for the same reasons as -O and since -O2 take a lot longer to compile most of the time and usually with little benefit. {{{ghc-options: -ffi}}} or {{{-fffi}}} use extensions: ForeignFunctionInterface. Once #190 is implemented then {{{ghc-options: -fvia-C}}} will be unnecessary too. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/191> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 9

Re: GHC's CPP and Cabal's unlit
by Alistair Bayley 02 Feb '08

02 Feb '08

> > It would be nice if we can find an unlit extension that is compatible > > with the H98 requirement and alo allows useful behaviour for haddock. I have completed changes to the Unlit module, and also a change to the Haddock module (to run unlit before cpp). darcs patches attached. I'd love to know what the official approach to testing is. I have written a test module which exercises the Unlit module, but I'm not sure how to tie it in to any existing test infrastructure. At the moment I just have it sitting in tests/unlit. Thanks, Alistair

5 23

building only the docs
by Peter Gammie 31 Jan '08

31 Jan '08

Do you expect this to work? <setup> clean <setup> configure <setup> haddock <setup> install I get, e.g.: $ runghc Setup install Installing: /home/peteg/lib/HaXml-1.13.2/ghc-6.6.1 Installing: /home/peteg/bin Setup.hs: Error: Could not find module: Text.ParserCombinators.HuttonMeijerWallace with any suffix: ["hi"] whereas if I swap "build" for "haddock" line the "install" line does not complain about the lack of docs to install. cheers peter

3 5

[Hackage] #190: extension ForeignFunctionInterface should imply -fvia-C for ghc
by Hackage 30 Jan '08

30 Jan '08

#190: extension ForeignFunctionInterface should imply -fvia-C for ghc --------------------------+------------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.1 Platform: Linux | --------------------------+------------------------------------------------- I think the recommended practice with ghc is for code that uses FFI to compile via C to get the benefit of checking against C headers. So using that extension should imply not just -fffi but -fvia-C for ghc. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/190> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #180: configure should warn if a declared licence file is missing
by Hackage 27 Jan '08

27 Jan '08

#180: configure should warn if a declared licence file is missing ---------------------+------------------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Cabal | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.4.2 Platform: Linux | ---------------------+------------------------------------------------------ There are a few packages around which declare {{{ license-file: LICENSE }}} but then that LICENSE file actually does not exist. Currently we do not discover this until we try and install at which point we get the unhelpful error: {{{ setup: LICENCE: copyFile: does not exist (No such file or directory) }}} It would be much more helpful to users and developers alike if we warned in the configure step if the file was missing. This is partly a transitional issue, since older versions of Cabal did not install license files at all, so it never noticed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/180> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #164: bad error message when using configuration flags that were not defined
by Hackage 26 Jan '08

26 Jan '08

#164: bad error message when using configuration flags that were not defined ------------------------------+--------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.0 Severity: minor | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.4.2 Platform: Linux | ------------------------------+--------------------------------------------- Using a flag in an if condition when that flag has not been previously defined gives an unhelpful error message: {{{ -- flag foo never declared: if flag(foo) blah: else other: }}} We get the error message: {{{ cabal-setup: Environment not defined for all free vars }}} The error is reported by {{{Distribution.Configuration.simplifyCondTree}}} but the error should probably be checked for much earlier. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/164> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #170: pkg-config uses a more general version scheme
by Hackage 26 Jan '08

26 Jan '08

#170: pkg-config uses a more general version scheme ---------------------+------------------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: low | Milestone: Component: Cabal | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.4.2 Platform: Linux | ---------------------+------------------------------------------------------ From {{{HsOpenSSL.cabal}}} {{{ --PkgConfig-Depends: openssl >= 0.9.7l -- We really should use this instead of the configure -- script but Cabal 1.2.2.0 can't handle the weird version -- scheme of OpenSSL. }}} For example: {{{ $ pkg-config --modversion openssl 0.9.8f }}} Currently Cabal tries to map pkg-config versions to the standard {{{Version}}} type which only allows for a sequence of numbers. pkg-config uses just strings to represent package versions. It uses code lifted from rpm to compare version strings. See the {{{compare_versions}}} function in {{{pkg-gconfig-0.22/pkg.c}}} from http://pkgconfig.freedesktop.org/releases/pkg-config-0.22.tar.gz -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/170> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #195: Specify include and library paths that are used for building the package only
by Hackage 24 Jan '08

24 Jan '08

#195: Specify include and library paths that are used for building the package only ---------------------+------------------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.3.0 Severity: normal | Keywords: jgoerzen(a)complete.org Difficulty: normal | Ghcversion: 6.8.1 Platform: Linux | ---------------------+------------------------------------------------------ From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293523 {{{ Specify include and library paths that are used for building the package only, and do not end up in the GHC packages file. }}} I think this needs more explanation. There is certainly a use case for includes that are used to pre-process Haskell code since they are never needed when building dependent packages. On the other hand, library paths to find libraries to link to are always required by dependent packages as far as I know since to link an executable using a package that uses a library we have to specify the library and search path. There is no way with GHC to limit where a C header file might be needed. If a header file is needed to compile a package, then the header file might also be needed to compile code that uses the package due to cross- package inlining. If GHC does gain the feature to limit the scope of where C headers are required then we will want to support that in Cabal, possibly via package-local headers. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/195> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #194: add sanity checking to version numbers
by Hackage 23 Jan '08

23 Jan '08

#194: add sanity checking to version numbers ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.1 Platform: Linux | ----------------------------------+----------------------------------------- http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=308260 {{{ It's been reported that there are packages with version numbers like 5.01 which will be parsed as 5.1 by cabal. }}} This should be easy to do. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/194> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #165: The ./configure configure hook should complain if ./configure does not exist
by Hackage 21 Jan '08

21 Jan '08

#165: The ./configure configure hook should complain if ./configure does not exist ---------------------+------------------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.4.2 Platform: Linux | ---------------------+------------------------------------------------------ We often have problems with people not running auto(re)conf before Setup configure, and things breaking later on. The hook that runs ./configure should fail if ./configure doesn't exist; it probably shouldn't give any suggestion on how to create it, as people will blindly follow the suggestion and one size probably won't fit all. This essentially depends on the proposals to split up hooks into smaller, composable parts. Ian Lynagh -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/165> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3