January 2009 - cabal-devel

[Hackage] #386: Cabal changelog is not in user's guide
by Hackage 09 Mar '09

09 Mar '09

#386: Cabal changelog is not in user's guide ----------------------------+----------------------------------------------- Reporter: Deewiant | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.10.1 Platform: | ----------------------------+----------------------------------------------- The Cabal user's guide doesn't contain the changelog. This means, for instance, that one can't view it in the offline documentation distributed with GHC. It's also not directly linked from http://www.haskell.org/cabal/, making it altogether a bit better hidden than it should be. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/386> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #303: cabal clean: Error while removing dist/: dist/setup: removeDirectory: unsatisified constraints (Directory not empty)
by Hackage 09 Mar '09

09 Mar '09

#303: cabal clean: Error while removing dist/: dist/setup: removeDirectory: unsatisified constraints (Directory not empty) ----------------------------+----------------------------------------------- Reporter: simonmar | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.4.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- cabal clean has a problem on Windows and Unix with NFS that causes it to fail when using a custom `Setup.hs`. The problem is that we compile `Setup.hs` to `dist/setup/setup`, and then invoke `dist/setup/setup clean` which is supposed to remove the whole of the `dist` tree, including the running binary. This causes problems on Windows where running binaries can't be deleted, and also on NFS where deleting the running binary leaves a `.nfs` file behind, preventing the parent directory from being deleted. {{{ > cabal clean -v Creating dist/setup (and its parents) dist/setup/setup clean --verbose=2 --distpref=dist cleaning... Error while removing dist/: dist/setup: removeDirectory: unsatisified constraints (Directory not empty) > ls -lr dist total 36 -rw-rw-r-- 1 simonmar GHC 13069 2008-06-23 11:34 setup-config drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:34 setup/ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 build/ ~/darcs/ghc-paths > ls -lra dist total 52 -rw-rw-r-- 1 simonmar GHC 13069 2008-06-23 11:34 setup-config drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:34 setup/ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 build/ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 ../ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:34 ./ ~/darcs/ghc-paths > ls -lRa dist dist: total 52 drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:34 ./ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 ../ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 build/ drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:34 setup/ -rw-rw-r-- 1 simonmar GHC 13069 2008-06-23 11:34 setup-config dist/build: total 52 drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 ./ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:34 ../ drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:32 autogen/ drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:32 GHC/ -rw-rw-r-- 1 simonmar GHC 3657 2008-06-23 11:32 HSghc-paths-0.1.o -rw-rw-r-- 1 simonmar GHC 4404 2008-06-23 11:32 libHSghc-paths-0.1.a dist/build/autogen: total 24 drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:32 ./ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 ../ -rw------- 1 simonmar GHC 990 2008-06-23 11:32 Paths_ghc_paths.hs dist/build/GHC: total 32 drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:32 ./ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:32 ../ -rw-rw-r-- 1 simonmar GHC 895 2008-06-23 11:32 Paths.hi -rw-rw-r-- 1 simonmar GHC 3824 2008-06-23 11:32 Paths.o dist/setup: total 16 drwxrwxr-x 2 simonmar GHC 4096 2008-06-23 11:34 ./ drwxrwxr-x 4 simonmar GHC 4096 2008-06-23 11:34 ../ }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/303> 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] #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

[Hackage] #470: bad error message when a package transtively depends on two versions of the same one
by Hackage 03 Mar '09

03 Mar '09

#470: bad error message when a package transtively depends on two versions of the same one ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ The following error appears like nonsense: {{{ cabal: dependencies conflict: ghc-6.10.1 requires process ==1.0.1.0 however process-1.0.1.0 was excluded because ghc-6.10.1 requires process ==1.0.1.1 }}} It actually means that there's some package ghc depends on that now is built against the newer process. It should tell the name of the other package(s), too. This is made worse by user-installed packages of the same version shadowing global ones, in this case there is no real error. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/470> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2