February 2010 - cabal-devel

[Hackage] #532: Can't find libraries on Windows (Cabal 1.6.0.2)
by Hackage 27 Mar '10

27 Mar '10

#532: Can't find libraries on Windows (Cabal 1.6.0.2) ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.2 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: Windows | ----------------------------+----------------------------------------------- When trying to install the com-1.2.2 package from the Hackage tarball, configure reports that it cannot find the header file "include/WideStringSrc.h", which is part of the com-1.2.2 source, and is clearly there; and that it cannot find the libraries "kernel32", "user32", etc which are standard system libraries (the corresponding .lib files are part of the Platform SDK), even after giving it the library paths in every possible way (environment variable, command line option, modifying the "com.cabal" file). The former problem was mysteriously eliminated by some random modification of the .cabal file (namely, rearranging the order of the includes). The OS is Windows XP (servicepack 2). Everything works fine with Cabal 1.6.0.1. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/532> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #465: default global install on windows is a problem
by Hackage 21 Mar '10

21 Mar '10

#465: default global install on windows is a problem ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.8 Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: Windows | ----------------------------+----------------------------------------------- Lots of windows users have problems installing things globally. Some are using multi-user systems. More are using Vista where it seems that even when they are running as administrator they cannot install files in `C:\Program Files\`. We should revisit the decision to install globally and see if we cannot find a default that works better. Failing by default is bad. We may also want to try to improve the checking beforehand to check if we would have permissions to write into the target directories. If not we can fail at configure time rather than waiting until install time and failing ungracefully. This needs someone who knows and cares about windows. Particularly for the Vista aspects. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/465> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #639: 'source-repository' should not necessarily require 'cabal-version >= 1.6'
by Hackage 20 Mar '10

20 Mar '10

#639: 'source-repository' should not necessarily require 'cabal-version >= 1.6' ----------------------------+----------------------------------------------- Reporter: andersk | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- `Distribution.PackageDescription.Check` has this check: {{{ -- check use of "source-repository" section , checkVersion [1,6] (not (null (sourceRepos pkg))) $ PackageDistInexcusable $ "The 'source-repository' section is new in Cabal-1.6. " ++ "Unfortunately it messes up the parser in earlier Cabal versions " ++ "so you need to specify 'cabal-version: >= 1.6'." }}} However, I’ve found that Cabal 1.2 can successfully parse a cabal file with a 'source-repository' section (with a warning), _if_ that section is at the end of the file. Perhaps the check could be loosened to allow (and suggest) this? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/639> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #251: link to the latest version of a package tar file
by Hackage 20 Mar '10

20 Mar '10

#251: link to the latest version of a package tar file ----------------------------------+----------------------------------------- Reporter: ross(a)soi.city.ac.uk | 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: | ----------------------------------+----------------------------------------- Dan Corson suggests: it would be good to have links to latest versions of a package file available for download. for example: something like {{{ http://hackage.haskell.org/packages/archive/arrows/latest.tar.gz }}} would be a link to {{{ http://hackage.haskell.org/packages/archive/arrows/0.4/arrows-0.4.tar.gz }}} this would greatly simplify automating installs. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/251> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

2 5

[Hackage] #520: Use nice Unicode characters for inequalities
by Hackage 20 Mar '10

20 Mar '10

#520: Use nice Unicode characters for inequalities ----------------------------------+----------------------------------------- Reporter: Porges | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: 1.6.0.1 Severity: minor | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: Platform: | ----------------------------------+----------------------------------------- This is a terribly minor request, but it would make the display nicer :) In dependency restrictions, instead of displaying (>=), (<=), use (≥), (≤). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/520> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #570: Include distributions status on package page
by Hackage 19 Mar '10

19 Mar '10

#570: Include distributions status on package page --------------------------------+------------------------------------------- Reporter: nomeata | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: Severity: normal | Keywords: patch Difficulty: unknown | Ghcversion: Platform: | --------------------------------+------------------------------------------- Hi, I would find it very helpful if the package pages on hackage would include information as to which packages are available in distributions (Debian, arch, gentoo...). I have implemented a patch that reads this information from a simple formatted text and displays it. I have also implemented the generation of the list for Debian at http://people.debian.org/~nomeata/cabalDebianMap.txt, see README. A cronjob should fetch this regularly (maybe 4 times a day). To add distributions, you need to create the appropriate list (URLs are optional), add the distribution name to DistroMap.hs and put the lists in the right location. It would be great if this could be deployed. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/570> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 23

[Hackage] #587: Get all of Hackage indexed by Google Code Search
by Hackage 19 Mar '10

19 Mar '10

#587: Get all of Hackage indexed by Google Code Search ----------------------------+----------------------------------------------- Reporter: tibbe | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: miscellaneous | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Google Code Search is a really nice (and fast!) way of browsing lots of code online. It would be cool if the whole of Hackage would be searchable from Code Search. One useful thing is to be able to find all mentions of a function in all packages on Hackage. Another good thing is to be able to find examples of how other people use libraries (i.e. use Code Search as a learning tool). What we need to make this work is to host and XML file (that we could regenerate N times daily) in a public location (e.g. http://hackage.haskell.org/sitemap.xml) Instructions on how to set it up: http://www.google.com/support/webmasters/bin/answer.py?hl=en&answer=75224 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/587> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #526: hugs-options aren't passed to ffihugs
by Hackage 18 Mar '10

18 Mar '10

#526: hugs-options aren't passed to ffihugs ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- Options in hugs-options aren't passed through to ffihugs, most importantly -98 and +o are the ones we'd like to pass. For enabling the +o flag Hugs-Sept06 does not honor: * pragma {-# LANGUAGE !OverlappingInstances #-} * pragma {-# OPTIONS_HUGS +o #-} * cabal extensions: !OverlappingInstances And the -98 flag has similar issues. Therefore this is a real problem. Immediate solution: The options set in hugs-options should be passed to ffihugs as well. As of Cabal 1.6 they are not passed (verified by Duncan Coutts). The two programs accept all the same options, so this is valid. Ideal solution: Based on the extensions field, Cabal should automatically determine whether -98 and +o need to be enabled (for both hugs and ffihugs). A simple example demonstrating this bug can be found in Darcs repo http://community.haskell.org/~wren/cabal-ffihugstest -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/526> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #527: CPP not called before ffihugs
by Hackage 18 Mar '10

18 Mar '10

#527: CPP not called before ffihugs ----------------------------+----------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.6.0.1 Severity: normal | Keywords: Difficulty: unknown | Ghcversion: Platform: | ----------------------------+----------------------------------------------- When building for Hugs, if CPP is being used in conjunction with FFI, then cpp/cpphs is not called before ffihugs is called. Thus, users must pass an -F flag to ffihugs in order to declare a code filter (and must pass all cpp-options to -F manually). For example: {{{ --ffihugs-option=-F'cpp -P -traditional -D__HUGS__ -D__BLAH__' }}} This requires duplicating the build specifications, which defeats the point of Cabal. Also it leads to tricky issues about ensuring the proper level of quoting/escaping. (e.g. using the plural, --ffihugs-options=..., breaks it. Wrapping the -F'cpp...' in double quotes breaks it.) A simple example of this bug can be seen in Darcs repo http://community.haskell.org/~wren/cabal-ffihugstest -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/527> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #284: Cannot upload packages that require specific cabal versions
by Hackage 18 Mar '10

18 Mar '10

#284: Cannot upload packages that require specific cabal versions --------------------------------+------------------------------------------- Reporter: guest | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: hackageDB website | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | --------------------------------+------------------------------------------- I have a package that requires a custom Setup.lhs.The package works for ghc 6.8.x and 6.6.x and, thus, the Setup.lhs script was designed to work with Cabal 1.2.x, the one that comes with ghc 6.8.x. This is clearly indicated in the cabal-version field. However, if I try to upload this package to hackage I get this error: {{{ hint-0.2.0.1/hint.cabal: This package requires Cabal version: >=1.2&&<1.3 }}} As a workaround I used cabal-version: >= 1.2 but now, although the description explicitly says that it works with ghc 6.8.x, hackage indicates that it fails to build. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/284> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5