February 2008 - cabal-devel

[Hackage] #196: ability to specify custom args to haddock
by Hackage 26 May '08

26 May '08

#196: ability to specify custom args to haddock ---------------------+------------------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.1 Platform: Linux | ---------------------+------------------------------------------------------ From http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=293523 {{{ The ability to specify custom args to haddock, which is necessary to do things such as build docs that encompass parts of other packages }}} We can pass extra options to any program via the generic configure --$PROG-options= mechanism however for haddock this is not very useful since we also have to call haddock for another purpose and passing extra options there causes problems. Since the debian bug was filed there are several more feature of the haddock command, perhaps they solve the problem. If not, perhaps the problem could be explained further. What problem are we trying to solve here that would require passing extra options to haddock, and what extra options would one use? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/196> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #174: cabal-install tries to upgrade the base package
by Hackage 21 May '08

21 May '08

#174: cabal-install tries to upgrade the base package ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.6 Platform: Linux | ----------------------------+----------------------------------------------- When using ghc-6.6.x, with some packages, cabal-install tries to upgrade the base package to satisfy dependnecies. This is obviously impossible. The dependency resolution mechanism needs to be taught this fact. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/174> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7

[Hackage] #226: Cabal install should upgrade in the correct order.
by Hackage 21 May '08

21 May '08

#226: Cabal install should upgrade in the correct order. ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ Also, `cabal upgrade package-name` should probably upgrade that packages and dependencies, but not other packages. Here was my session with darcs cabal-install 2008-01-31: {{{ $ cabal upgrade Upgrading the following packages: cgi-3001.1.5.2 hmatrix-0.2.0.0 pcre-light-0.3 regex-base-0.93.1 regex-compat-0.91 regex-posix-0.93.1 TypeCompose-0.3 xhtml-3000.0.2.2 zlib-0.4.0.2 Downloading 'cgi-3001.1.5.2'... [... cgi upgrades fine ...] Configuring regex-compat-0.91... setup: At least the following dependencies are missing: regex-base >=0.93, regex-posix >=0.93 Downloading 'TypeCompose-0.3'... Downloading 'xhtml-3000.0.2.2'... Downloading 'zlib-0.4.0.2'... cabal: Error: some packages failed to install: zlib-0.4.0.2 xhtml-3000.0.2.2 TypeCompose-0.3 regex-compat-0.91 regex-posix-0.93.1 regex-base-0.93.1 pcre-light-0.3 hmatrix-0.2.0.0 $ cabal upgrade regex-base Upgrading the following packages: hmatrix-0.2.0.0 pcre-light-0.3 regex-base-0.93.1 regex-compat-0.91 regex-posix-0.93.1 TypeCompose-0.3 xhtml-3000.0.2.2 zlib-0.4.0.2 'hmatrix-0.2.0.0' is cached. [... everything through TypeCompose upgrades fine ...] 'xhtml-3000.0.2.2' is cached. Configuring xhtml-3000.0.2.2... 'zlib-0.4.0.2' is cached. Configuring zlib-0.4.0.2... [... zlib upgrades fine ...] cabal: Error: some packages failed to install: xhtml-3000.0.2.2 $ cabal upgrade Upgrading the following packages: xhtml-3000.0.2.2 'xhtml-3000.0.2.2' is cached. Configuring xhtml-3000.0.2.2... [... succeeds ...] }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/226> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #214: Package security
by Hackage 21 May '08

21 May '08

#214: Package security ------------------------------+--------------------------------------------- Reporter: duncan | Owner: Type: task | Status: new Priority: normal | Milestone: Component: misc | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: project(> week) | Ghcversion: 6.8.2 Platform: | ------------------------------+--------------------------------------------- It'd be nice to avoid getting hacked by a trojaned package. This task is to: * survey the issue * consider the threats * see what solutions other systems use * consider the cost/benefit trade-offs in various security solutions * propose something -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/214> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

3 17

[Hackage] #253: Check for invalid operating system names
by Hackage 23 Apr '08

23 Apr '08

#253: Check for invalid operating system names ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.2 Platform: | ----------------------------------+----------------------------------------- Some packages (eg hslogger-1.0.4) have incorrect operation system names tests: {{{ if !os(win32) Build-Depends: unix }}} It's incorrect because there is no such operating system "win32", there is "windows" which is an alias for "mingw32". So we should check for these problems. At the moment the OS is just a String . We should decide if we want to use an enumeration or leave it more flexible and just warn about unknown ones. Checks are easy to add, see `Distribution/PackageDescription/Check.hs` -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/253> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #224: allow specifying package version constraints to configure
by Hackage 20 Apr '08

20 Apr '08

#224: allow specifying package version constraints to configure ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Cabal-1.4 Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Currently, configure considers the version constraints from the `build- depends` of the `.cabal` file. Of the available packages that satisfy those constraints it picks the highest version. This is not always what we want. The user might want to pick a specific version of a dependency (eg for testing or to avoid a known dud). cabal-install certainly wants to specify package versions exactly because it does its own dependency resolution and it may well end up not picking the latest version of an available dependency, eg to ensure consistent versions of a dependent package (see #220). So the dependencies would be specified just as in `build-depends`, for example: {{{ cabal configure --constraint="bytestring == 0.9.0.1" }}} (suggestions for a better flag name welcome) However it must only be for dependencies that the package actually depends on. It should be an error to specify constraints on packages that could never be used by the package we are configuring. The fact that package dependencies can be conditional complicates this slightly. To be precise, we could say that if the package name is not mentioned in the flattened package description then it is an error. If the package named in the constraint happens merely not be use in the selected configuration then it is not an error and the constraint is discarded. So an external package manager (like cabal-install) can control exactly how a package will be configured by setting all the use flags and precisely constraining all the dependencies. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/224> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #233: case of Boolean values "true" and "false" should not matter
by Hackage 27 Mar '08

27 Mar '08

#233: case of Boolean values "true" and "false" should not matter ----------------------------+----------------------------------------------- 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: | ----------------------------+----------------------------------------------- The Cabal documentation does not specify the formatting of Boolean values "true" and "false". Hence it seems reasonable to assume that case does not matter, as it does not matter for any field name. However, the ghc- based implementation of Cabal seems to only accept init-caps "True" and "False". -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/233> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

2 10

[Hackage] #166: sdist puts Happy-generated .hs files in the wrong place
by Hackage 25 Mar '08

25 Mar '08

#166: sdist puts Happy-generated .hs files in the wrong place ---------------------+------------------------------------------------------ Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.6 Platform: Linux | ---------------------+------------------------------------------------------ I want to use sdist to generate source distributions of Happy that don't depend on Happy, and hence come with the Happy-generated .hs files for the parsers. When I try this, the source files are included, but in the root of the tree, whereas Cabal seems to look for them in `dist/build`. I can move them by hand and re-generate the tarball, and that works. I'm fairly sure this worked with older versions of Cabal. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/166> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #202: add a flag/config to make cabal use sudo/su/.. when installing with --global
by Hackage 19 Mar '08

19 Mar '08

#202: add a flag/config to make cabal use sudo/su/.. when installing with --global ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: global install sudo Difficulty: normal | Ghcversion: 6.8.2 Platform: Linux | ---------------------------------+------------------------------------------ cabal install --global usually fails because of missing privileges. sudo cabal install --global is quite messy since every intermediate file is then owned by root, so other tasks that wouldn't need privileges at all, now requires them to handle those files. I propose to add the possibility to configure a command to use when running the equivalent of "runhaskell Setup install" on the package. So that the user can set it in ~/.cabal/config and it will always be used when install --global is run. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/202> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #221: a generic way for cabal-install to specify external dependencies
by Hackage 18 Mar '08

18 Mar '08

#221: a generic way for cabal-install to specify external dependencies ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: Linux | ----------------------------+----------------------------------------------- Cabal-install needs a way to specify external dependencies, so that re- install can be made as automatic as possible. The fact that Cabal records the 3rd digit version in the path indicates a diligent user has to re- install all the packages on every new 3rd-digit dot release. Exanples are HDBC-ODBC and regex-pcre. This issue was raised in http://www.mail-archive.com/haskell-cafe@haskell.org/msg37001.html It was discussed before and Tim had one suggestion: http://www.mail-archive.com/haskell-cafe@haskell.org/msg33790.html I suggest to have a config-replacement file (or a section in .cabal/config) as such: package: SDL include-dirs: c:\libs\SDL\include When cabal-install attempts to install SDL in this case, it will replace the line "include-dirs" in <package>.cabal with what is suggested in the config-replacement file. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/221> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7