January 2012 - cabal-devel

[Hackage] #874: cabal: Couldn't read cabal file "HDBC/2.2.6.1/HDBC.cabal"
by Hackage 03 Mar '12

03 Mar '12

#874: cabal: Couldn't read cabal file "HDBC/2.2.6.1/HDBC.cabal" ---------------------------------+------------------------------------------ Reporter: arpho | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.3 Severity: normal | Keywords: hdbc install Difficulty: unknown | Ghcversion: 6.10.1 Platform: Linux | ---------------------------------+------------------------------------------ Hi, I would like to install hdbc,I use the command sudo cabal install hdbc, but the terminal returns me this: cabal: Couldn't read cabal file "HDBC/2.2.6.1/HDBC.cabal" what's wrong? thanks you in advance -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/874> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #883: Single command to figure out ghc[i] options needed to compile a single file
by Hackage 03 Mar '12

03 Mar '12

#883: Single command to figure out ghc[i] options needed to compile a single file ---------------------------------+------------------------------------------ Reporter: barsoap | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ I'm thinking of a {{{cabal options <file.hs>}}} command that 1. locates the proper .cabal file for <file.hs> 2. parses that .cabal 3. outputs all options necessary to compile that file as cabal build would do it, that is, {{{-isrc -idist/build/autogen (-Xwhatever)* -hide-all- packages (-package-id whatever)*}}} There's already cabal-ghci on hackage which has one half of the equation, but packages are missing. (which happen to be available via grep and sed from cabal_macros.h...) Needing those options comes up when e.g. working with vim's haskellmode on a cabal project: Most if not all cabal projects' files just fail to compile with default options. Having such a command would give a bullet- proof, non-hackish and low-tech way to integrate cabal with any such IDE tool. (Do note that just building with cabal isn't enough, while haskellmode can parse the resulting warnings and errors, it doesn't stand a chance to figure out types, among other things, that way) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/883> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #902: cabal install --enable-tests --only-dependencies fails to come up with a complete install plan
by Hackage 03 Mar '12

03 Mar '12

#902: cabal install --enable-tests --only-dependencies fails to come up with a complete install plan ---------------------------------+------------------------------------------ Reporter: tibbe | Owner: ttuegel Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Something is wrong with how test suite dependencies are included in the install plan: {{{ $ git clone https://github.com/tibbe/hashable.git $ cd hashable $ cabal install --enable-tests --only-dependencies Resolving dependencies... Configuring deepseq-1.2.0.1... Preprocessing library deepseq-1.2.0.1... Building deepseq-1.2.0.1... [1 of 1] Compiling Control.DeepSeq ( Control/DeepSeq.hs, dist/build/Control/DeepSeq.o ) Registering deepseq-1.2.0.1... Installing library in /Users/tibbe/.cabal/lib/deepseq-1.2.0.1/ghc-7.0.4 Registering deepseq-1.2.0.1... Configuring text-0.11.1.9... cabal: At least the following dependencies are missing: HUnit ==1.2.*, QuickCheck ==2.4.*, test-framework ==0.4.*, test-framework-hunit ==0.2.*, test-framework-quickcheck2 ==0.2.* cabal: Error: some packages failed to install: text-0.11.1.9 failed during the configure step. The exception was: ExitFailure 1 }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/902> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #894: Add benchmark support
by Hackage 29 Feb '12

29 Feb '12

#894: Add benchmark support ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Today, a user needs to rely on external tools, such as Make, to build benchmarks associated with a package. This has a couple of issues: * It's hard to have both Make (which builds the benchmark) and Cabal (which builds the library) pick the same versions of package dependencies. This leads to compilation errors when the user installs or removes some packages from his/her system. * It's hard to accurately track what needs to be rebuilt when, forcing the user to rebuild more than necessary, which wastes time. Proposal: Add a new `.cabal` file section for benchmarks, modeled after the "test-suite" section. Usage: {{{ cabal configure --enable-benchmarks cabal build cabal bench # results are written to stdout }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/894> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #888: runTests deprecated message should be more helpful
by Hackage 16 Feb '12

16 Feb '12

#888: runTests deprecated message should be more helpful ----------------------------+----------------------------------------------- Reporter: dsfox | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.8.0.6 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- It would be great if this message explained what the new testing interface was, where to find it, and optimally how to quickly create something more or less equivalent to the runTests function so we can get on with our lives. :) Warning: In the use of `runTests' (imported from Distribution.Simple, but defined in Distribution.Simple.UserHooks): Deprecated: "Please use the new testing interface instead!" -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/888> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

Patch to let hackage-server build with GHC <= 7.4.1
by Bas van Dijk 14 Feb '12

14 Feb '12

Hi, Attached is a patch which lets hackage-server build with GHC <= 7.4.1. It would be great if somebody could apply it. Cheers, Bas

2 4

patch: --enable-tests and --only-dependencies
by Antoine Latter 03 Feb '12

03 Feb '12

Hi Cabal, When trying to use "cabal install --enable-tests --only-dependencies" it appears to be passing the "--enable-tests" option down to the dependent packages during build. This isn't what I want at all - I only want to use the "--enable-tests" flag for the purpose of building an install plan. In addition, the dependency solver doesn't solve dependencies as if dependent packages would be built with "--enable-tests", so the "configure" step for these packages fails due to missing dependencies. My proposed fix is to strip the 'configTests' flag from the ConfigFlags after building the install plan but before doing the installation itself, because passing 'enable-tests' to the 'configure' step during 'cabal install' doesn't make much sense to me anyway. An alternative fix would be to have a separate set of config flags per source package to be installed, with --enable-tests only turned on for the original target packages. A patch is attached. Antoine

3 5

Paths_pkg fails to build with NoImplicitPrelude
by Dag Odenhall 20 Jan '12

20 Jan '12

Hello, A .cabal file like the following: Name: pkgname Library Extensions: NoImplicitPrelude Other-Modules: Paths_pkgname ... results in a failed build due to Paths_pkgname relying on ImplicitPrelude. It would be better if 1) Paths_pkgname could somehow ignore the Extensions listed in the .cabal file, or, 2) It simply included an import of Prelude or a LANGUAGE pragma enabling ImplicitPrelude, although this solution might still be prone to breakage by other extensions. -- Dag

1 0

Adding ldconfig to Distribution/Simple/Program/Builtin.hs
by Dave Tapley 13 Jan '12

13 Jan '12

The subject says it all really, could we add ldconfig to "the collection of unconfigured and configured programs"? This collection is defined in this module: Distribution.Simple.Program.Builtin Dave,

1 0

Patch to read package-specific cabal-install config
by Carl Baatz 10 Jan '12

10 Jan '12

Hi all, for packages that aren't for public consumption, we would like to specify a private Hackage repo location. The simplest way we could think of to do this was to read a config file in the same format as the user config (~/.cabal/config) from the current directory and let any flags set in that file override the user config. The attached patch implements this, reading any file with a .cabal-install extension (including '.cabal-install'). It errors out if more than one .cabal-install file is found or if there's a parse error on the .cabal-install file. Does this sound like a good idea? If not, any ideas for alternative ways of handling non-public packages? Many thanks, Carl

2 4