December 2008 - cabal-devel

[Hackage] #428: cabal update should use rsync over tree instead of GET on a monolithic file
by Hackage 27 Jan '09

27 Jan '09

#428: cabal update should use rsync over tree instead of GET on a monolithic file ----------------------------+----------------------------------------------- Reporter: claus | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- `cabal update` appears to download a compressed tarball (>600k and growing), which is larger than most packages, takes a while over a slow line, and doesn't provide much info (`-v` just adds low-level details). using `rsync` over the relevant parts of the directory tree ought to be faster (increasingly so as hackage keeps growing), use less bandwith, and be able to tell me which package descriptions have changed (although it would be nice to limit the latter info to new packages and changes to installed packages). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/428> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[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] #419: cabal-install: upgrade complains about missing .cabal file
by Hackage 26 Jan '09

26 Jan '09

#419: cabal-install: upgrade complains about missing .cabal file ---------------------------------+------------------------------------------ Reporter: jimburton | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.4.0.2 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ I am using cabal-install 0.5.2. I have previously installed cgi (and other packages) locally. Now when I try to upgrade them all: Resolving dependencies... cabal: Couldn't read cabal file "./cgi/3001.1.7.1/cgi.cabal" I presumed that the starting point in that path was ~/.cabal/packages/hackage.haskell.org. In cgi/3001.1.7.1 there is just the tarball for the package but opening it and putting the .cabal file in the right place didn't help. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/419> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[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

[Hackage] #177: Include-dirs, extra-lib-dirs with spaces doesn't work under Windows
by Hackage 22 Jan '09

22 Jan '09

#177: Include-dirs, extra-lib-dirs with spaces doesn't work under Windows ----------------------+----------------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.6 Platform: Windows | ----------------------+----------------------------------------------------- Trying to build the HDBC-PostGreSQL database driver[1] revealed some poor handling of pathames under Windows. The package requires that the paths to postgre header and libraries files be added to the .cabal file. My initial attempt was the obvious: {{{ include-dirs: C:\Program Files\PostgreSQL\8.2\include, C:\Program Files\PostgreSQL\8.2\include\server, . extra-lib-dirs: C:\Program Files\PostgreSQL\8.2\include, C:\Program Files\PostgreSQL\8.2\include\server }}} However, the package would not build. The include files "pg_config.h" and some others were not found. Using single or double quotes did not help. Finally, I moved the installation to "C:\pgsql" and updated the .cabal file: {{{ include-dirs: C:\pgsql\include, C:\pgsql\include\server, . extra-lib-dirs: C:\pgsql\lib }}} And the package built. It seems the spaces in the first path caused the problem. For reference, this it the configure output on my machine: {{{ Configuring HDBC-postgresql-1.0.1.0... configure: Dependency base-any: using base-2.1.1 configure: Dependency mtl-any: using mtl-1.0.1 configure: Dependency HDBC>=1.0.0: using HDBC-1.0.1 configure: Dependency parsec-any: using parsec-2.0 configure: Using install prefix: C:\Program Files configure: Binaries installed in: C:\Program Files\Haskell\bin configure: Libraries installed in: C:\Program Files\Haskell\HDBC- postgresql-1.0.1.0\ghc-6.6.1 configure: Private binaries installed in: C:\Program Files\HDBC- postgresql-1.0.1.0 configure: Data files installed in: C:\Program Files\Common Files\HDBC- postgresql-1.0.1.0 configure: Using compiler: c:\ghc\ghc-6.6.1\bin\ghc.exe configure: Compiler flavor: GHC configure: Compiler version: 6.6.1 configure: Using package tool: c:\ghc\ghc-6.6.1\bin\ghc-pkg.exe configure: Using ar found on system at: c:\ghc\ghc-6.6.1\bin\ar.exe configure: Using haddock found on system at: C:\haddock\haddock-0.8\haddock.exe configure: No pfesetup found configure: Using ranlib found on system at: c:\MinGW\bin\ranlib.exe configure: Using runghc found on system at: c:\ghc\ghc-6.6.1\bin\runghc.exe configure: Using runhugs found on system at: C:\Program Files\WinHugs\runhugs.exe configure: No happy found configure: No alex found configure: Using hsc2hs: c:\ghc\ghc-6.6.1\bin\hsc2hs.exe configure: No c2hs found configure: No cpphs found configure: No greencard found }}} Feel free to email me at jgbailey AT gmail DOT com for more info. [1] Version 1.0.1.0 available at http://hackage.haskell.org/cgi-bin /hackage-scripts/package/HDBC-postgresql-1.0.1.0. HDBC is also required. I used 1.0.1, available at http://hackage.haskell.org/cgi-bin/hackage- scripts/package/HDBC-1.0.1. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/177> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 10