January 2012 - cabal-devel

Re: [Hackage] #402: Automatic hoogle database for installed packages
by Hackage 05 Jan '12

05 Jan '12

#402: Automatic hoogle database for installed packages ---------------------------------+------------------------------------------ Reporter: Peaker | Owner: dschoepe Type: enhancement | Status: assigned Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ Comment(by elga): * [http://www.releve-identite-operateur.fr/numbero-de-virgin-mobile.html virgin mobile] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/402#comment:8> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #627: sdist drops executable permissions for files in the tarball
by Hackage 05 Jan '12

05 Jan '12

#627: sdist drops executable permissions for files in the tarball ----------------------------+----------------------------------------------- Reporter: draconx | Owner: Type: defect | Status: closed Priority: normal | Milestone: Cabal-1.10 Component: Cabal library | Version: Severity: normal | Resolution: fixed Keywords: | Difficulty: unknown Ghcversion: | Platform: Linux ----------------------------+----------------------------------------------- Comment(by elga): * [http://www.releve-identite-operateur.fr/rio-simyo.html simyo] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/627#comment:5> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #382: 'cabal ghci' mode
by Hackage 05 Jan '12

05 Jan '12

#382: 'cabal ghci' mode ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: Severity: major | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ Comment(by elga): * [http://www.releve-identite-operateur.fr/numbero-de-virgin-mobile.html virgin mobile] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/382#comment:13> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

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

05 Jan '12

#165: The ./configure configure hook should complain if ./configure does not exist ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: closed Priority: normal | Milestone: Component: Cabal library | Version: 1.2.0 Severity: normal | Resolution: fixed Keywords: | Difficulty: very easy (<1 hour) Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Comment(by elga): * [http://www.releve-identite-operateur.fr/rio-simyo.html simyo] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/165#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #403: Bad error message when running ./configure fails to find sh
by Hackage 05 Jan '12

05 Jan '12

#403: Bad error message when running ./configure fails to find sh ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: closed Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: HEAD Severity: minor | Resolution: fixed Keywords: | Difficulty: very easy (<1 hour) Ghcversion: 6.10.1 | Platform: Windows ----------------------------+----------------------------------------------- Comment(by elga): * [http://www.releve-identite-operateur.fr/rio-bouygues.html rio bouygues] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/403#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #335: GHC_PACKAGE_PATH disrespected
by Hackage 05 Jan '12

05 Jan '12

#335: GHC_PACKAGE_PATH disrespected ----------------------------------+----------------------------------------- Reporter: cjs | Owner: kmcallister Type: defect | Status: assigned Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.3 Platform: Other Unix | ----------------------------------+----------------------------------------- Comment(by elga): [http://www.releve-identite-operateur.fr simyo] -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/335#comment:8> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #245: Cabal should support hsc2hs's stub .c feature
by Hackage 03 Jan '12

03 Jan '12

#245: Cabal should support hsc2hs's stub .c feature ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: low | Milestone: _|_ Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Changes (by acowley): * cc: acowley@… (added) Comment: I've also run into this issue. Using #def is very convenient for wrapping a C interface (e.g. to handle passing structs by value). To work around the cabal limitation, one can either use a Makefile or a custom Setup.hs to manually invoke hsc2hs in the src directory before running the usual cabal install. This requires that the generated *_hsc.c files be specified in the .cabal file. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/245#comment:7> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Data files for test suites
by Antoine Latter 02 Jan '12

02 Jan '12

Hi Cabal, Is their a recommended way of specifying data files to use with a test-suite? I want to test being able to parse binary data in a backwards compatible way, so would like the test data to be in source control. My current plan is to assume that the working directory in a test suite is always going to by the same directory as my .cabal file. Thanks, Antoine

2 1