November 2008 - cabal-devel

[Hackage] #262: Check for required C libraries during configure
by Hackage 18 Feb '09

18 Feb '09

#262: Check for required C libraries during configure ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Cabal should check for required C libraries and other non-Haskell dependencies at the configure stage, rather than just waiting for the linker to fail with an obscure error message during the build stage. Error messages should be helpful for the typical Cabal user, who should not be assumed to know anything about C libraries or linking. That is not so simple. For example: The haddock package current requires the C libraries for readline, due to its dependency on the GHC API. If that library is missing, the user should have some way of figuring out how do the right thing on the given platform - for most Linux distros, install the readline-dev package (as opposed to just readline), for Mac OS X download the GNUreadline framework from the GHC website and drag it into the appropriate Frameworks folder depending on whether this is Tiger and below or Leopard and above, etc. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/262> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 16

[Hackage] #236: Installed package config refers to nonexisting haddock interface and html files
by Hackage 04 Feb '09

04 Feb '09

#236: Installed package config refers to nonexisting haddock interface and html files ----------------------------+----------------------------------------------- Reporter: kolmodin | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Cabal generates the {{{haddock-interfaces}}} and {{{haddock-html}}} package fields even if the haddock documentation is not built nor installed. Instead of assuming haddock is used, it should add the fields iff needed upon register (install = copy + register), where enough information should be available to make a more clever installation. Example {{{ghc-pkg describe binary}}} built without haddock: {{{ name: binary version: 0.4.1 license: BSD3 copyright: maintainer: Lennart Kolmodin, Don Stewart <dons(a)galois.com> stability: provisional homepage: http://www.cse.unsw.edu.au/~dons/binary.html package-url: description: Efficient, pure binary serialisation using lazy ByteStrings. Haskell values may be encoded to and form binary formats, written to disk as binary, or sent over the network. Serialisation speeds of over 1 G\/sec have been observed, so this library should be suitable for high performance scenarios. category: Data, Parsing author: Lennart Kolmodin <kolmodin(a)dtek.chalmers.se> exposed: True exposed-modules: Data.Binary Data.Binary.Put Data.Binary.Get Data.Binary.Builder hidden-modules: import-dirs: /usr/lib/binary-0.4.1/ghc-6.8.2 library-dirs: /usr/lib/binary-0.4.1/ghc-6.8.2 hs-libraries: HSbinary-0.4.1 extra-libraries: extra-ghci-libraries: include-dirs: includes: depends: base-3.0.1.0 bytestring-0.9.0.4 base-3.0.1.0 containers-0.1.0.1 array-0.1.0.0 hugs-options: cc-options: ld-options: framework-dirs: frameworks: haddock-interfaces: /usr/share/doc/binary-0.4.1/html/binary.haddock haddock-html: /usr/share/doc/binary-0.4.1/html }}} Both {{{/usr/share/doc/binary-0.4.1/html/binary.haddock}}} and {{{/usr/share/doc/binary-0.4.1/html}}} are (rightfully) missing in the installation. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/236> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #368: The "optimization" option in ~/.cabal/config does not work
by Hackage 01 Feb '09

01 Feb '09

#368: The "optimization" option in ~/.cabal/config does not work ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.4.0.1 Severity: minor | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: Linux | ---------------------------------+------------------------------------------ Running cabal install $package with "optimization: True" uncommented in ~/.cabal/config results in an error: cabal: Command.optionToFieldDescr: feature not implemented -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/368> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #316: on Windows, include paths with spaces not properly passed to c2hs
by Hackage 26 Jan '09

26 Jan '09

#316: on Windows, include paths with spaces not properly passed to c2hs ----------------------------+----------------------------------------------- Reporter: jwlato | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.4.0 Severity: normal | Keywords: include-dirs, c2hs Difficulty: normal | Ghcversion: 6.8.3 Platform: Windows | ----------------------------+----------------------------------------------- On windows, path names with spaces aren't passed to build tools properly. In a new project, with a source file Test.chs and a cabal file with (boilerplate excluded) {{{ #!c exposed-modules: Test build-tools: c2hs include-dirs: "C:\\Program Files\\include" }}} then attempting "runhaskell Setup.lhs build -v" indicates that the following is executed: {{{ #!c c:\Program Files\Haskell\bin\c2hs.exe --include=dist\build --cppopts=-D__GLASGOW_HASKELL__=608 --cppopts=-IC:\Program Files\include --output-dir=dist\build --output=Test.hs Test.chs }}} This command fails because c2hs interprets Files\include as a filename to process. The -IC:\Program Files ... should be quoted to preserve the space in the path. I have attached a test.cabal and Test.chs file that demonstrate the problem. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/316> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #412: build-reports: option is invalid in a config file
by Hackage 26 Jan '09

26 Jan '09

#412: build-reports: option is invalid in a config file ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ With darcs (tonight) cabal and cabal-install, I see the generated .cabal/config includes the line '-- build-reports:', suggesting that this is a valid configuration option. However, it is not. If one uncomments it to 'build-reports: True', then Cabal warns and apparently ignores one's configuration as corrupt: gwern@craft:29302~>cabal update Warning: Error parsing config file /home/gwern/.cabal/config:9: "True" Warning: Using default configuration. Downloading package list from server 'http://hackage.haskell.org/packages/archive' The syntax is valid, the True is correct, it's not listed as being part of a section. further, --build-reports is a valid CLI option: gwern@craft:29304~>rm .cabal/config && mv config .cabal && cabal install --build-reports ztail [ 9:21PM] Resolving dependencies... Downloading hinotify-0.2... [1 of 1] Compiling Main ( /tmp/TMPhinotify-0.2/hinotify-0.2/Setup.lhs, /tmp/TMPhinotify-0.2/hinotify-0.2/dist/setup/Main.o ) Linking /tmp/TMPhinotify-0.2/hinotify-0.2/dist/setup/setup ... Downloading ztail-1.0... ........ Either the default config is lying/wrong, or the build-reports: option is busted. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/412> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #392: Use the constraint solver for cabal configure
by Hackage 25 Jan '09

25 Jan '09

#392: Use the constraint solver for cabal configure ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.6 Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ Currently `cabal install` and `cabal upgrade` use the constraint solver to select the dependencies while `cabal configure` just selects the highest version of each package. That means it sometimes picks bad combinations where `cabal install` would do something smarter. It also means it does not use preferences like `base < 4`. However for `cabal configure` it's important that the solver not fail and prevent configuring at all. If the solver cannot find a consistent solution we should probably warn and fall back to the existing behavior. We may also want to prevent `cabal configure` from picking anything other than the current installed packages. Though again that's likely to increase the chance of failure. Perhaps if there is no solution for the current installed packages then it should check if there would be a solution if we allowed re-installs and if so say so in the warning message. If not fall back to the highest versions of everything as now. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/392> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #200: Feature request: Simplify the profiling process
by Hackage 25 Jan '09

25 Jan '09

#200: Feature request: Simplify the profiling process ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Add Setup.(l)hs options that: 1) tells ghc to make a profiling library; 2) tells ghc to make a profiling executable 3) pass on the (a) -auto or (b) -auto-all option 4) Let you do (1)-(2)-(3a) or (1)-(2)-(3b) with a single option, instead of three. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/200> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 10

[Hackage] #361: Add documentation location information to cabal list package command
by Hackage 22 Jan '09

22 Jan '09

#361: Add documentation location information to cabal list package command ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- It would be useful for the cabal list package command to return information about whether the documentation for the package is installed, and if so, where it might be found. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/361> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #362: Disallow uploads of libraries that provide binaries called 'test' and similar
by Hackage 22 Jan '09

22 Jan '09

#362: Disallow uploads of libraries that provide binaries called 'test' and similar ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Some libraries (example, haskore), provide an executable called 'test' or 'Test' or other similarly named private test programs. These are however installed onto the users system, or prevented from doing so, as they conflict with /usr/bin/test uploading should prevent and warn if people use unix builtin names as executables, particularly 'test'. -- don stewart -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/362> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #395: Warn about dependencies like parsec <= 2.1.0.0
by Hackage 22 Jan '09

22 Jan '09

#395: Warn about dependencies like parsec <= 2.1.0.0 ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.3 Platform: | ----------------------------------+----------------------------------------- Cabal should warn about dependencies like `parsec <= 2.1.0.0`. It's almost certainly a mistake given the conventional semantics of version numvers. Something like `foo < 2.0` is quite common and it's relatively harmless so there's probably no point in warning. On the other hand `foo < 2.0.0` is weird. It says `foo-2.0` is ok, but `foo-2.0.0` or `foo-2.0.0.1` is not. Something like `foo <= 2.0` is a definately weird though since it excludes bug fixes like `foo-2.0.0.1` -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/395> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5