June 2009 - cabal-devel

that test hook
by Peter Gammie 01 Jun '09

01 Jun '09

Hello, I see from the archives that this hook is much unloved. How is one supposed to use it? The arguments to the function are underspecified. What is the Bool? I want access to the command-line flags, or at least verbosity settings. How do I do that? I envisage testing like so (approx): Setup test file Setup test dir Setup test --verbose Has anyone used it in anger? cheers peter

3 3

Paths module in package description or not?
by Henning Thielemann 01 Jun '09

01 Jun '09

Consider http://code.haskell.org/mohws/mohws.cabal When I include Paths_mohws as Other-Modules, 'cabal haddock' aborts with: thielema@euler:~/programming/haskell/mohws> cabal haddock Preprocessing library mohws-0.2.0.1... Preprocessing executables for mohws-0.2.0.1... Running Haddock for mohws-0.2.0.1... Warning: The documentation for the following packages are not installed. No links will be generated to these packages: rts-1.0 Preprocessing library mohws-0.2.0.1... Preprocessing executables for mohws-0.2.0.1... cabal: can't find source for module Paths_mohws When I remove Paths_mohws from Other-Modules then the library and executables in the package can be built successfully. But when I compile an executable outside the package, then I get a linker error: parallelweb> cabal install Resolving dependencies... Configuring parallelweb-0.0.2... Preprocessing executables for parallelweb-0.0.2... Building parallelweb-0.0.2... Linking dist/build/parallelweb/parallelweb ... /home/thielema/.cabal/lib/mohws-0.2.0.1/ghc-6.10.3/libHSmohws-0.2.0.1.a(Configuration.o): In function `sfyj_info': (.text+0x2d1f): undefined reference to `mohwszm0zi2zi0zi1_Pathszumohws_a7_closure' /home/thielema/.cabal/lib/mohws-0.2.0.1/ghc-6.10.3/libHSmohws-0.2.0.1.a(Configuration.o): In function `seCS_info': (.text+0x86bb): undefined reference to `__stginit_mohwszm0zi2zi0zi1_Pathszumohws_' collect2: ld returned 1 exit status cabal: Error: some packages failed to install: parallelweb-0.0.2 failed during the building phase. The exception was: exit: ExitFailure 1 I use: $ cabal --version cabal-install version 0.6.0 using version 1.6.0.1 of the Cabal library Which way is the intended one? Include Paths_mohws in package description or not? In general, shall automatically generated files appear in Cabal file? I think they should not, since they are not part of the distribution tarball. So can I consider the linker error being a bug?

2 1

patch applied (cabal): Remove a couple unused imports.
by Duncan Coutts 01 Jun '09

01 Jun '09

Mon Jun 1 12:29:32 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Remove a couple unused imports. M ./Distribution/Simple/Hugs.hs -1 +2 M ./Distribution/Simple/LHC.hs -1 +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090601192932-adfee-1d3ee287…

1 0

patch applied (cabal): Ban upwardly open version ranges in dependencies on base
by Duncan Coutts 01 Jun '09

01 Jun '09

Mon Jun 1 12:16:29 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Ban upwardly open version ranges in dependencies on base Fixes ticket #435. This is an approximation. It will ban most but not all cases where a package specifies no upper bound. There should be no false positives however, that is cases that really are always bounded above that the check flags up. Doing a fully precise test needs a little more work. M ./Distribution/PackageDescription/Check.hs -6 +62 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090601191629-adfee-a891c10e…

1 0

patch applied (cabal): Split requireProgram into two different functions
by Duncan Coutts 01 Jun '09

01 Jun '09

Mon Jun 1 10:48:46 PDT 2009 Duncan Coutts <duncan(a)haskell.org> * Split requireProgram into two different functions Now requireProgram doesn't take a version range and does not check the program version (indeed it doesn't need to have one). The new function requireProgramVersion takes a required program version range and returns the program version. Also update callers. Also fixes the check that GHC has a version number. M ./Distribution/Simple/Configure.hs -6 +17 M ./Distribution/Simple/GHC.hs -12 +12 M ./Distribution/Simple/Haddock.hs -6 +8 M ./Distribution/Simple/Hugs.hs -2 +2 M ./Distribution/Simple/JHC.hs -6 +6 M ./Distribution/Simple/LHC.hs -10 +11 M ./Distribution/Simple/NHC.hs -13 +14 M ./Distribution/Simple/Program.hs -9 +33 M ./Distribution/Simple/SrcDist.hs -2 +2 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20090601174846-adfee-072ec549…

1 0

Re: Patch to register XmlSyntax and RegularPatterns as known extensions
by Duncan Coutts 01 Jun '09

01 Jun '09

On Thu, 2009-05-28 at 23:00 +0200, Niklas Broberg wrote: > Hi all, > > I'd like to have concrete XML syntax (HSP) and regular expression > pattern syntax (HaRP) registered in Language.Haskell.Extension. The > attached patch registers XmlSyntax and RegularPatterns as constructors > in the Language.Haskell.Extension.Extension data type, along with > haddock documentation. Since there were no objections I've applied the patch, so both extensions are now registered. Duncan

1 0