- cabal-devel - Haskell.org

patch applied (cabal-install): Update HTTP dep in the bootstrap script
by Duncan Coutts 23 Jan '09

23 Jan '09

Fri Jan 23 08:07:00 PST 2009 Duncan Coutts <duncan(a)haskell.org> * Update HTTP dep in the bootstrap script M ./bootstrap.sh -1 +2 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20090123160700-adfee-…

1 0

patch applied (cabal-install): Improve error message when ghc or ghc-pkg are mismatched or not found
by Duncan Coutts 23 Jan '09

23 Jan '09

Fri Jan 23 08:05:50 PST 2009 Duncan Coutts <duncan(a)haskell.org> * Improve error message when ghc or ghc-pkg are mismatched or not found M ./bootstrap.sh -1 +5 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20090123160550-adfee-…

1 0

patch applied (cabal-install): Don't use grep -e, solaris does not like it
by Duncan Coutts 23 Jan '09

23 Jan '09

Fri Jan 23 08:04:43 PST 2009 Duncan Coutts <duncan(a)haskell.org> * Don't use grep -e, solaris does not like it M ./bootstrap.sh -2 +2 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20090123160443-adfee-…

1 0

Problems with install-includes
by George Giorgidze 23 Jan '09

23 Jan '09

Hi, In my project I am using C include/header files that are hierarchically nested into folders. These header files are used to compile the Haskell package and everything is fine with the compilation process. I want these include files also to be installed with the package. From the online documentation of Cabal I learned that there exists specific field for this purpose called install-includes. However, it does not work when include files are hierarchically nested into folders. Here is relevant part of the cabal file I am using. include-dirs: cbits/sundials/include install-includes: nvector/nvector_serial.h when I am issuing cabal install command I am getting the following error: cabal: Error: some packages failed to install: Hydra-0.1 failed during the final install step. The exception was: /home/ggg/.cabal/lib/Hydra-0.1/ghc-6.10.1/include/nvector: copyFile: does not exist (No such file or directory) It seems to me that cabal forgets to create parent directories for folder nested include files. For not-nested include files install-includes filed works fine. The Cabal version I am using is 1.6.0.1. The cabal-install version I am using is 0.6.0 Currently, as a workaround I am using data-files field to install include files. However, I would like to see this issue fixed (I assume it is a bug). Cheers, George -- George Giorgidze http://www.cs.nott.ac.uk/~ggg/

2 2

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

23 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] #456: `cabal info pkg` command
by Hackage 23 Jan '09

23 Jan '09

#456: `cabal info pkg` command ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ The output for `cabal list` cannot be too verbose or it looses its purpose as a search. For details on an individual package we could use `cabal info foo` instead. This could present the info for the package in greater detail. For example, most of the meta-data from the .cabal file or installed package info. In particular the bug report url (#449) and the location of any installed documentation (#361). Alternatively we could do this in `cabal list` with some flag to get more detailed information. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/456> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

patch applied (cabal-install): Fix some FIXMEs and do some TODOs in the list command
by Duncan Coutts 23 Jan '09

23 Jan '09

Thu Jan 22 16:48:10 PST 2009 Duncan Coutts <duncan(a)haskell.org> * Fix some FIXMEs and do some TODOs in the list command Now properly prints if the haddock docs are installed and if the tarball is cached. It did print them before but it was lying. M ./Distribution/Client/List.hs -108 +150 View patch online: http://darcs.haskell.org/cabal-install/_darcs/patches/20090123004810-adfee-…

1 0

[Hackage] #473: Cabal-1.6 does not work on Windows with ghc-6.6.x
by Hackage 22 Jan '09

22 Jan '09

#473: Cabal-1.6 does not work on Windows with ghc-6.6.x ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.6 Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.6.1 Platform: Windows | ----------------------------------+----------------------------------------- http://haskell.org/pipermail/cabal-devel/2009-January/004622.html The problem is the `writeFileAtomic` function calls the compat version of `openNewBinaryFile` and that fails on Windows with ghc-6.6. Specifically it is the `fdToHandle` that throws the exception. The crux is: {{{ fd <- withCString filepath $ \ f -> c_open f oflags 0o666 h <- fdToHandle (fromIntegral fd) }}} However `fdToHandle` fails with the exception {{{ fdGetMode: invalid argument }}} This is because in ghc-6.6.x, the `fdToHandle` calls `fdGetMode` and passes the result to `openFd`: {{{ fdToHandle :: FD -> IO Handle fdToHandle fd = do mode <- fdGetMode fd let fd_str = "<file descriptor: " ++ show fd ++ ">" openFd fd Nothing False{-XXX!-} fd_str mode True{-bin mode-} }}} However `fdGetMode` is described thusly: {{{ fdGetMode fd = do #if defined(mingw32_HOST_OS) || defined(__MINGW32__) -- XXX: this code is *BROKEN*, _setmode only deals with O_TEXT/O_BINARY }}} Note that the `openBinaryTempFile` function does not call `fdToHandle`, instead it bypasses it and calls `openFd` directly. The `openFd` function is exported from `GHC.Handle` so we could use it in `Distribution.Compat.TempFile` -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/473> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

patch applied (cabal): Fix openNewBinaryFile on Windows with ghc-6.6
by Duncan Coutts 22 Jan '09

22 Jan '09

Thu Jan 22 09:21:00 PST 2009 Duncan Coutts <duncan(a)haskell.org> * Fix openNewBinaryFile on Windows with ghc-6.6 fdToHandle calls fdGetMode which does not work with ghc-6.6 on windows, the workaround is not to call fdToHandle, but call openFd directly. Bug reported by Alistair Bayley, ticket #473. M ./Distribution/Compat/TempFile.hs +4 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090122172100-adfee-87f2e4f0…

1 0

[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