December 2008 - cabal-devel

[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

patch applied (cabal): Ban ghc-options: --make
by Duncan Coutts 23 Dec '08

23 Dec '08

Tue Dec 23 09:06:21 PST 2008 Duncan Coutts <duncan(a)haskell.org> * Ban ghc-options: --make I dunno, some people... M ./Distribution/PackageDescription/Check.hs +4 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081223170621-adfee-be8bef41…

1 0

patch applied (cabal): Update changelog for 1.6.0.2 release
by Duncan Coutts 23 Dec '08

23 Dec '08

Thu Dec 11 06:22:02 PST 2008 Duncan Coutts <duncan(a)haskell.org> * Update changelog for 1.6.0.2 release M ./changelog +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081211142202-adfee-b98a0c2b…

1 0

patch applied (cabal): Make the compiler PackageDB stuff more flexible
by Duncan Coutts 23 Dec '08

23 Dec '08

Thu Dec 11 06:16:49 PST 2008 Duncan Coutts <duncan(a)haskell.org> * Make the compiler PackageDB stuff more flexible We support using multiple package dbs, however the method for specifying them is very limited. We specify a single package db and that implicitly specifies any other needed dbs. For example the user or a specific db require the global db too. We now represent that stack explicitly. The user interface still uses the single value method and we convert internally. M ./Distribution/Simple/Compiler.hs +20 M ./Distribution/Simple/Configure.hs -8 +19 M ./Distribution/Simple/GHC.hs -6 +12 M ./Distribution/Simple/JHC.hs -3 +7 M ./Distribution/Simple/LHC.hs -8 +21 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081211141649-adfee-e37bf8bd…

1 0

[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

[Hackage] #327: should require minimum c2hs version of 0.15
by Hackage 22 Dec '08

22 Dec '08

#327: should require minimum c2hs version of 0.15 ----------------------------------+----------------------------------------- Reporter: duncan | Owner: Type: defect | 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: | ----------------------------------+----------------------------------------- Cabal does not work with c2hs older than 0.15. With older c2hs versions the .hs file ends up in the wrong location in the build tree. If we find that c2hs is needed for the build then we should check that it meets this minimum version. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/327> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 2

[Hackage] #383: Hsc2hs preprocessor does not ensure that gcc has been found.
by Hackage 22 Dec '08

22 Dec '08

#383: Hsc2hs preprocessor does not ensure that gcc has been found. ----------------------------+----------------------------------------------- Reporter: nominolo | Owner: Type: defect | Status: new Priority: normal | Milestone: Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.10.1 Platform: | ----------------------------+----------------------------------------------- When trying to configure with an inplace GHC on Windows, Cabal dies with an irrefutable pattern match error. The offending line is: {{{ Just gccProg = lookupProgram gccProgram (withPrograms lbi) }}} in {{{D.S.PreProcess.ppHsc2hs}}}. The problem was that configure didn't find gcc in its expected place ({{{ghcBase </> "gcc.exe"}}}) and Cabal didn't check that it did before running the preprocessor. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/383> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

Warning: Unknown extensions: ViewPatterns
by Neil Mitchell 22 Dec '08

22 Dec '08

Hi It appears cabal doesn't know ViewPatterns are a valid extension: hlint$ cabal install --global Resolving dependencies... Configuring hlint-1.0.0.1... Warning: Unknown extensions: ViewPatterns Preprocessing executables for hlint-1.0.0.1... Building hlint-1.0.0.1... Thanks Neil

2 1

Wildcard syntax
by Neil Mitchell 22 Dec '08

22 Dec '08

Hi, I have base == 4.0.* in my hlint cabal file (http://www.cs.york.ac.uk/fp/darcs/hlint/hlint.cabal) Does that require Cabal 1.4 or 1.6? Apparently 1.2 fails to parse it, but with a cabal-version >= 1.2 declaration I don't get any warnings from Cabal 1.6. So what is the minimum verison for the version wildcard, and why doesn't cabal warn me I got it wrong? Thanks Neil

2 1