- cabal-devel - Haskell.org

[Hackage] #519: .cpphs files are processed using GHC's built-in CPP instead of cpphs
by Hackage 07 Mar '09

07 Mar '09

#519: .cpphs files are processed using GHC's built-in CPP instead of cpphs ----------------------------+----------------------------------------------- Reporter: Deewiant | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Currently, if you need to use `cpphs`, the only way of going about it is to define a custom `PreProcessor` in your `Setup.hs` and using it as an override in `hookedPreProcessors`. A seemingly sensible way of making this easier would be that `.cpphs` files prefer being processed by `cpphs` instead of GHC's built-in CPP. (Most people probably just use `{-# LANGUAGE CPP #-}` in a `.hs` for the latter anyway.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/519> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #290: Cabal does some work behind the back of hooks
by Hackage 07 Mar '09

07 Mar '09

#290: Cabal does some work behind the back of hooks ----------------------------+----------------------------------------------- Reporter: igloo | 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: | ----------------------------+----------------------------------------------- Cabal does some work behind the back of hooks, e.g. with `q.cabal`: {{{ name: q version: 1 exposed-modules: Bar build-type: Custom }}} and `Setup.hs`: {{{ module Main (main) where import Distribution.Simple import Distribution.Simple.Setup import System.Cmd main :: IO () main = defaultMainWithHooks myHooks myHooks :: UserHooks myHooks = simpleUserHooks { confHook = \x flags -> do let flags' = flags { configDistPref = Flag "foo" } lbi <- (confHook simpleUserHooks) x flags' system "ls" return lbi, postConf = \args flags pd lbi -> do system "ls" let flags' = flags { configDistPref = Flag "foo" } (postConf simpleUserHooks) args flags' pd lbi return () } }}} a `dist` directory magically appears between the configure hook and the postconf hook: {{{ $ ./Setup configure Configuring q-1... Setup Setup.hi Setup.hs Setup.o foo q.cabal Setup Setup.hi Setup.hs Setup.o dist foo q.cabal $ ls -l dist -rw-r--r-- 1 ian ian 6411 Jun 8 12:02 setup-config }}} The reason I want to do this is so that `Setup.hs` can take care of building itself in multiple ways, using different dist directories. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/290> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #263: Multiple compilers of the same version confuse Cabal
by Hackage 07 Mar '09

07 Mar '09

#263: Multiple compilers of the same version confuse Cabal ----------------------------+----------------------------------------------- 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: | ----------------------------+----------------------------------------------- It often happens that two or more copies of the same version of the same compiler are installed on a system. For example, the compiler can be installed with an installation package, or be built from the source tarball, or from darcs, or using MacPorts. If a package is installed for each of these copies of the compiler while allowing Cabal to use the default installation location each time, Cabal will always use the exact same folder. This leads to mayhem and anarchy. Proposed solution: Cabal should also use the base path of the compiler when it constructs the directory name for the package, not just the compiler name and version. For example: If I install a package foo-1.2.3.4 --with- compiler=/opt/local/bin/ghc-6.8.2 and the installation base path is /usr/local, then Cabal should install the package into /usr/local/foo-1.2.3.4/opt_local_ghc-6.8.2 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/263> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #464: install needs a --package-conf=FILE flag
by Hackage 07 Mar '09

07 Mar '09

#464: install needs a --package-conf=FILE flag ----------------------------+----------------------------------------------- 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.3 Platform: | ----------------------------+----------------------------------------------- It's not possible to use a non-standard package configuration file while installing at the moment. It would be very convenient to have. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/464> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #430: HackageDB is overly pessimistic about HPC.
by Hackage 07 Mar '09

07 Mar '09

#430: HackageDB is overly pessimistic about HPC. --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.3 Platform: | --------------------------------+------------------------------------------- HackageDB wont accept packages that have optional support for HPC. Having packages on Hackage with optional support for HPC can be very useful at times. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/430> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #518: reconfigure command that uses the previous configure command
by Hackage 05 Mar '09

05 Mar '09

#518: reconfigure command that uses the previous configure command ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Sometimes I make a small change to the .cabal file such as adding an exposed module. Cabal then won't let me build without performing a "cabal configure", however I often have a few flags set, so what I'd like to issue instead is: "cabal reconfigure" which means perform a "cabal configure" with the current set of use flags. This would be similar to, and a complement to bug 294. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/518> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

Re: Request to make a validation item on the hackage uploader a soft warning rather than a hard fail
by Andrea Vezzosi 04 Mar '09

04 Mar '09

We resolved to drop support for Cabal < 1.4 in happstack, most users will install using cabal-install anyway. Thanks, Andrea Vezzosi. On Wed, Mar 4, 2009 at 11:52 PM, Matthew Elder <matt(a)mattelder.org> wrote: > Hello All, > > I am trying to upload a release package for happstack 0.2. Right now it > gives me an error because I added dist/build/autogen to my hs-source-dirs. > You can find the output of my error here: > > http://hpaste.org/fastcgi/hpaste.fcgi/view?id=2104#a2104 > > I have been working with Andrea Vezzossi (Saizan) to try to figure out the > best way to handle this situation; he says that this must stay in the .cabal > file to be compatible with Cabal 1.2.4.0 (version that ships with ghc > 6.8.3). Is there any way you guys could make this a soft fail when uploading > to hackage rather than a hard fail? This seems reasonable at least for > awhile until everyone has a chance to upgrade to the latest versions of ghc. > > Thanks in advance guys! > > -- > Need somewhere to put your code? http://patch-tag.com > Want to build a webapp? http://happstack.com >

1 0

[Hackage] #398: better support for static linking
by Hackage 03 Mar '09

03 Mar '09

#398: better support for static linking ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- Generating statically linked binaries on different platforms requires a bit of knowledge about what flags to pass to ghc. It would be nice to just be able to `cabal configure --enable-static-executable` or something and have that pass the extra `-optl-static` and whatever ghc options are required. If it's not possible to generate static binaries it should make some attempt at explaining why. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/398> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #424: build-depends in global section in new-style .cabal files are ignored
by Hackage 03 Mar '09

03 Mar '09

#424: build-depends in global section in new-style .cabal files are ignored ----------------------------+----------------------------------------------- Reporter: duncan | 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: | ----------------------------+----------------------------------------------- http://hpaste.org/12669 In a .cabal file like: {{{ name: music version: 0.0 cabal-version: >= 1.2 build-type: Simple build-depends: base == 4 library exposed-modules: Music }}} which uses new-style syntax but puts the build-depends in the global section, the build-depends get ignored. It should either warn or reject this, or it should automatically propagate such global options into each buildable component. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/424> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #442: remove old packages after successful update
by Hackage 03 Mar '09

03 Mar '09

#442: remove old packages after successful update ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.10.1 Platform: | ---------------------------------+------------------------------------------ After a successful `cabal update` command, the old version of the package could be removed. (It required to rebuild/reinstall all the dependent packages as well. It is reported in #441 ticket.) I do not think it should be a default behavior, but make it possible would be really nice. :) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/442> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2