November 2008 - cabal-devel

[Hackage] #379: compiler directive of cabal-install's config file is case sensitive
by Hackage 15 Jan '09

15 Jan '09

#379: compiler directive of cabal-install's config file is case sensitive ---------------------------------+------------------------------------------ Reporter: phigley | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: Mac OS | ---------------------------------+------------------------------------------ Using cabal-install 0.6.0 (and 1.6.0.1 of the Cabal library) the following line fails to parse in the config file (in ~/.cabal/config) : compiler: GHC which generates the following error : Warning: Error parsing config file /Users/peterhigley/.cabal/config:1: "GHC" Warning: Using default configuration. But changing it to this resolves the problem : compiler: ghc My config file was auto-generated from an older cabal-install. This is easiest to reproduce by running "cabal update". I am reproing on a Mac, but an e-mail was sent to haskell-cafe from a Windows user as well. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/379> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #358: cabal-install bootstrap.sh missing some dependencies
by Hackage 15 Jan '09

15 Jan '09

#358: cabal-install bootstrap.sh missing some dependencies ----------------------------------+----------------------------------------- Reporter: Araneidae | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.2 Platform: | ----------------------------------+----------------------------------------- The following dependencies are not checked for or installed by bootstrap.sh: `network`, `parsec`, `mtl`. On a fresh install of ghc 6.8.2 on Ubuntu 8.04 these packages are missing and need to be installed manually. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/358> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #359: Warn if package index is older than X days
by Hackage 14 Jan '09

14 Jan '09

#359: Warn if package index is older than X days ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.2 Platform: | ----------------------------------+----------------------------------------- People often trip up with getting older versions of packages than they expected because their package index is out of date. This is because people have to manually run `cabal update` occasionally. It would be nice if this could be done automatically, though we also need to support offline operation. In the mean time we should at least warn if the package index looks rather old. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/359> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #413: cabal --help should report the location of the config file
by Hackage 13 Jan '09

13 Jan '09

#413: cabal --help should report the location of the config file ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: cabal-install-0.6 Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: very easy (<1 hour) | Ghcversion: 6.8.3 Platform: | ----------------------------------+----------------------------------------- `cabal --help` should report the location of the config file. Perhaps we want some other info command to say what the current interesting bits of config are, like if we're doing global or per-user installs by default, where packages will be installed etc. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/413> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #373: doubled field
by Hackage 12 Jan '09

12 Jan '09

#373: doubled field ---------------------------------+------------------------------------------ Reporter: guest | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.4.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ---------------------------------+------------------------------------------ I have just uploaded a Cabal package to Hackage which has by accident two Homepage fields. But Hackage does only show the second of the two fields. I think either Hackage should support multiple Homepage fields or 'cabal check' should warn about doubled fields. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/373> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #410: cabal sdist does not call the sdist build hook in custom Setup.hs
by Hackage 12 Jan '09

12 Jan '09

#410: cabal sdist does not call the sdist build hook in custom Setup.hs ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ The `cabal sdist` command only runs the default actions, it does not call the sdist hook that gets called if you `runghc Setup sdist`. The problem is there is no external method for invoking the sdist hook. Calling `./setup sdist` performs the whole action, but we only want to prepare the tree and not tar it up, since `cabal sdist` uses internal tar code rather than calling an external tar program (which typically does not exist on windows). -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/410> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #348: Wrong login details for `cabal upload' is not handled gracefully
by Hackage 12 Jan '09

12 Jan '09

#348: Wrong login details for `cabal upload' is not handled gracefully ----------------------------+----------------------------------------------- Reporter: chrisdone | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.4 Component: Cabal library | Version: 1.4.0.1 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- Example: [[BR]] chris@chrisdesktop:~/haskell/lojban$ cabal upload dist/lojban-0.0.tar.gz[[BR]] Hackage username: foo[[BR]] Hackage password: bar[[BR]] Uploading dist/lojban-0.0.tar.gz...[[BR]] cabal: bsAuthGen wanted -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/348> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #342: Allow automatic resolving of conditionals on more than just build-depends
by Hackage 07 Jan '09

07 Jan '09

#342: Allow automatic resolving of conditionals on more than just build-depends -----------------------------+---------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: hard (< 1 day) | Ghcversion: 6.8.2 Platform: | -----------------------------+---------------------------------------------- We have several classes of dependency that we can express in .cabal files. The most obvious is other Haskell packages via the `build-depends` field. The others are: * C libs (`extra-libraries`) * C headers (`includes`) * other build tools (`build-tools`) * pkg-config packages (`pkgconfig-depends`) * MacOS X frameworks (`frameworks`) And we may end up with more, like Windows assemblies. If we know (by domain-specific means) what dependencies are available then we should be able to automatically resolve flag conditions that depend on them. So each one is it's own namespace and they have different representations of keys. Most use a name and some a version too. Currently `finalizePackageDescription` takes a `Maybe (PackageSet pkg)` as a way of testing if deps are available. We should generalise this to a dep testing function (which is essentially what `finalizePackageDescription` turns it into internally) on a type that has alternatives for each of the dependency namespaces. If we only had to generalise it for package constraints we might go for `Dependency -> [PackageId]` but how should we do it when we have multiple namespaces and some require version constraints and others do not. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/342> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #387: `cabal check` does not complain about incorrect `Cabal-Version` field
by Hackage 23 Dec '08

23 Dec '08

#387: `cabal check` does not complain about incorrect `Cabal-Version` field ----------------------------+----------------------------------------------- Reporter: Deewiant | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.10.1 Platform: | ----------------------------+----------------------------------------------- The validity of the `Cabal-Version` field is not verified in any way, making it all too easy to accidentally use a feature which isn't actually present in all the versions of Cabal the field allows. Sounds like something `cabal check` should do. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/387> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 4

[Hackage] #376: Allow constraint on using installed package versions
by Hackage 22 Dec '08

22 Dec '08

#376: Allow constraint on using installed package versions ---------------------------------+------------------------------------------ Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: cabal-install tool | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ---------------------------------+------------------------------------------ We allow command line args for adding version constraints. Internally the dependency resolver can use constraints on the installed status. We should allow such constraints to be given on the command line, and possibly in the cabal config file. We should probably also allow preferences to be given on the command line too. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/376> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5