July 2009 - cabal-devel

[Hackage] #299: Add changelog feature to hackagedb
by Hackage 22 Dec '09

22 Dec '09

#299: Add changelog feature to hackagedb --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | --------------------------------+------------------------------------------- It would be great if releases on hackagedb were required (or even permitted) to include short descriptions of the changes made since the last release. Currently there is no easy way to get this information for most packages, since many packages have no home page other than their hackagedb page. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/299> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 10

[Hackage] #478: allow comments on any line, don't require '.' for blank lines
by Hackage 19 Dec '09

19 Dec '09

#478: allow comments on any line, don't require '.' for blank lines ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- It confuses people that in `.cabal` files, comments can only appear on lines on their own, and not at the end of other lines. We should consider relaxing this as long as it can be done in a backwards compatible way. The only thing to worry about is command line flags like: {{{ cc-options: --some-flag }}} If we required a space after the `--` that might be sufficient. There are some tools that interpret `--` on its own as an argument, but usually only as a separator between flag arguments and non-flag arguments and we do not expect those to be given in .cabal files. We might like to allow `--` within quotes eg `"--"` however that's also not easy because of the syntax and format of .cabal files. They have no consistent lexical syntax, each field is parsed separately. The overall structure is parsed based on layout without parsing individual fields. In particular .cabal files are not tokenised. The second issue is easier. The original specification required that blank lines within a field include a leading `.` character. This applies to multi-paragraph descriptions. This syntax is totally unnecessary. The parser could cope fine without it. We should accept the convention for backwards compatibility but also allow ordinary blank lines. Multiple blank lines within a field should still be collapsed to one, and trailing blank lines within a field should be trimmed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/478> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #171: Add command to automagically create an initial cabal package
by Hackage 18 Dec '09

18 Dec '09

#171: Add command to automagically create an initial cabal package --------------------------+------------------------------------------------- Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal | Version: 1.2.2.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.6 Platform: Linux | --------------------------+------------------------------------------------- Don Stewart has a nice tool called mkcabal (http://www.cse.unsw.edu.au/~dons/code/mkcabal/) which creates an initial cabal package. It would be nice to have this built into the 'cabal' program itself so that "cabal create" or "cabal init" or similar would interactively create a cabal package. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/171> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 7

[Hackage] #516: Maintain central haddock module index.
by Hackage 18 Dec '09

18 Dec '09

#516: Maintain central haddock module index. ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: Platform: | ----------------------------+----------------------------------------------- The ghc api documentation includes a central index of [http://haskell.org/ghc/docs/latest/html/libraries/ all the modules in the core libraries]. Some people would like the same for all the modules provided by all the packages they have installed. See #206 for some of the previous discussion on this topic. The questions to resolve are where the index should be kept by default and how it should be configured (eg switched off). For example for a per-user install an index could live in `$HOME/.cabal/share/doc/index.html` but the equivalent is not appropriate for other prefixes like `/usr/local`. For global packages shipped by a distro the problem is much worse. We do not really want to have to have distro packages re-generating an html index every time they add and remove a package. Perhaps we should be looking at alternative solutions like using [http://live.gnome.org/devhelp devhelp] which can give easy access to installed documentation without maintaining a central index/catalog. Similar issues apply to a hoogle index. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/516> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #484: generalise version range syntax
by Hackage 18 Dec '09

18 Dec '09

#484: generalise version range syntax ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- The internal version range syntax allows arbitrary unions and intersections. The parser only allows two clauses and no brackets. See: http://haskell.org/pipermail/haskell-cafe/2009-January/054049.html {{{ I'm having some difficulty specifying dependencies in my .cabal file for a package I'm looking to upload to hackage soon. The difficulty is as follows. I basically want to specify parsec (>= 2.1 && < 3.0.0) || (> 3.0.0 && < 4) }}} I suggest we allow any number of clauses and brackets, to match the internal representation. We could also add `/=` or `!=` syntax since that is also easy to represent. It is harder to translate into other representations however we have a new view in terms of version ranges which should make it easier to do translations and to discover when the version range has more detail than can be represented in the target language (and maybe even approximate in such situations). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/484> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #485: preference on base version should only be applied for open constraints
by Hackage 18 Dec '09

18 Dec '09

#485: preference on base version should only be applied for open constraints ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ---------------------------------+------------------------------------------ Currently we apply the preference on the base version. That means that if you have base 3 and 4 available then for dependencies like: {{{ build-depends: base >= 2 }}} or {{{ build-depends: base >= 3 && < 5 }}} Then we end up picking base 3. That makes perfect sense in the first case. In the first case the developer clearly did not think about base 4. However in the second case they clearly have thought about it and yet we end up picking base 3. On balance it is probably better to pick base 4 in the second case even though both are allowed. One suggestion for how to handle soft constraints on the version of base is to say that we only apply the preference if the version is not bounded above. If it is bounded above then we use no preference and end up picking the highest version available. This policy cannot be expressed in the simple preferred versions syntax. It's probably ok to hard code it for base for now. This will require generalising the interface to the constraint solver to supply preferences in a slightly different form. It may need to be as a function from a list of possible versions to the selected version. The function would also be supplied with the package it's for, the dependency and the list of installed versions since it may want to take any of these into account and it is needed to express the above policy. This is related to the splitting of preferences into real preferences and hacks (see #483). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/485> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

[Hackage] #385: emgm package incorrectly shown as "program" but is "library and program"
by Hackage 01 Dec '09

01 Dec '09

#385: emgm package incorrectly shown as "program" but is "library and program" --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: Severity: minor | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | --------------------------------+------------------------------------------- The summary says it all. In the HackageDB package overview, it is shown whether packages contain libraries and/or programs, but this does not seem to work correctly in all cases, as emgm demonstrates. kosmikus -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/385> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #423: add option to fetch a single package without dependencies
by Hackage 27 Nov '09

27 Nov '09

#423: add option to fetch a single package without 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.3 Platform: | ----------------------------+----------------------------------------------- Right now, {{{cabal fetch}}} fetches all missing dependencies of a package along with its source. In some cases, in particular when studying code, those dependencies are not useful. It would be nice to have an option, say {{{--no-deps}}} to fetch just the specified packages. (This is related to {{{cabal unpack}}} -- see #390.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/423> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #562: cabal-install update fails going through a HTTP proxy (but not consistently)
by Hackage 13 Nov '09

13 Nov '09

#562: cabal-install update fails going through a HTTP proxy (but not consistently) ----------------------------+----------------------------------------------- Reporter: acid2 | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- I have installed Cabal, cabal-install and HTTP all from source on my Arch Linux machine, which has GHC 6.10.3 installed. When running {{{cabal update}}} this will occasionally work, but most often fails with the error: {{{cabal: user error (Codec.Compression.Zlib: premature end of compressed stream)}}} In this case, inspecting ~/.cabal/packages/hackage.haskell.org/00-index.tar.gz shows a file size that varies around 1-15K, rather than the expected ~900K. Attached are logs of `cabal-update` failing, and working: {{{ Downloading the latest package list from hackage.haskell.org Sending: GET http://hackage.haskell.org/packages/archive/00-index.tar.gz HTTP/1.1 User-Agent: cabal-install/0.6.2 Host: hackage.haskell.org proxy uri host: wwwcache.lancs.ac.uk, port: :8080 Creating new connection to wwwcache.lancs.ac.uk:8080 Received: HTTP/1.0 200 OK Date: Tue, 09 Jun 2009 13:50:46 GMT Server: Apache/2.2.3 (Debian) Last-Modified: Tue, 09 Jun 2009 09:53:44 GMT ETag: "3890c4-f8d7c-55909a00" Accept-Ranges: bytes Content-Length: 1019260 Content-Type: application/x-tar Content-Encoding: x-gzip Age: 854 X-Cache: HIT from wwwcache.lancs.ac.uk X-Cache-Lookup: HIT from wwwcache.lancs.ac.uk:8080 X-Cache: MISS from wwwcache.lancs.ac.uk X-Cache-Lookup: MISS from wwwcache.lancs.ac.uk:8080 Via: 1.0 wwwcache3.lancs.ac.uk:8080 (squid/2.6.STABLE22), 1.0 wwwcache1.lancs.ac.uk:8080 (squid/2.7.STABLE4) Connection: close Downloaded to /home/ollie/.cabal/packages/hackage.haskell.org/00-index.tar.gz }}} {{{ Downloading the latest package list from hackage.haskell.org Sending: GET http://hackage.haskell.org/packages/archive/00-index.tar.gz HTTP/1.1 User-Agent: cabal-install/0.6.2 Host: hackage.haskell.org proxy uri host: wwwcache.lancs.ac.uk, port: :8080 Creating new connection to wwwcache.lancs.ac.uk:8080 Received: HTTP/1.0 200 OK Date: Tue, 09 Jun 2009 13:50:46 GMT Server: Apache/2.2.3 (Debian) Last-Modified: Tue, 09 Jun 2009 09:53:44 GMT ETag: "3890c4-f8d7c-55909a00" Accept-Ranges: bytes Content-Length: 1019260 Content-Type: application/x-tar Content-Encoding: x-gzip Age: 875 X-Cache: HIT from wwwcache.lancs.ac.uk X-Cache-Lookup: HIT from wwwcache.lancs.ac.uk:8080 Via: 1.0 wwwcache3.lancs.ac.uk:8080 (squid/2.6.STABLE22) Proxy-Connection: close Downloaded to /home/ollie/.cabal/packages/hackage.haskell.org/00-index.tar.gz Reading available packages... }}} I was also asked to try running wget in verbose mode, this is the output: {{{ --2009-06-09 16:17:00-- http://hackage.haskell.org/packages/archive/00-index.tar.gz Resolving wwwcache.lancs.ac.uk... 194.80.32.11, 194.80.32.8, 194.80.32.9, ... Connecting to wwwcache.lancs.ac.uk|194.80.32.11|:8080... connected. Proxy request sent, awaiting response... HTTP/1.0 200 OK Date: Tue, 09 Jun 2009 13:50:46 GMT Server: Apache/2.2.3 (Debian) Last-Modified: Tue, 09 Jun 2009 09:53:44 GMT ETag: "3890c4-f8d7c-55909a00" Accept-Ranges: bytes Content-Length: 1019260 Content-Type: application/x-tar Content-Encoding: x-gzip Age: 1558 X-Cache: HIT from wwwcache.lancs.ac.uk X-Cache-Lookup: HIT from wwwcache.lancs.ac.uk:8080 Via: 1.0 wwwcache3.lancs.ac.uk:8080 (squid/2.6.STABLE22) Proxy-Connection: close Length: 1019260 (995K) [application/x-tar] Saving to: `00-index.tar.gz.2' 100%[===================================================================================================>] 1,019,260 --.-K/s in 0.09s 2009-06-09 16:17:00 (11.1 MB/s) - `00-index.tar.gz.2' saved [1019260/1019260] }}} -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/562> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 15

[Hackage] #403: Bad error message when running ./configure fails to find sh
by Hackage 10 Nov '09

10 Nov '09

#403: Bad error message when running ./configure fails to find sh ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: minor | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.10.1 Platform: Windows | ----------------------------------+----------------------------------------- For `build-type: Configure` we have to run `./configure`. On windows this will very often fail of course because they usually lack the `sh` program. Currently the error message users get is not great: {{{ sh: runGenProcess: does not exist (No such file or directory) }}} It would be nicer if they got a better message. Perhaps the way to do that is to catch the `DoesNotExist IOException` and re-throw a better message. Alternatively we could explicitly check for `sh` before invoking it. If it's not found on Windows then we could report that the package needs a unix-style command shell program eg from `mingw` to build. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/403> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1