- cabal-devel - Haskell.org

PROPOSAL: Extended syntax for package version range specifications
by Thomas Schilling 22 Jan '08

22 Jan '08

In order to make it easy for package package authors to describe correct and robust dependencies we (Duncan Coutts and I) propose the following syntactical extension to version range specifications in package files. (1) Wildcards ~ 1.2.* ~~> >= 1.2 && < 1.3 in general ~ x.y.* ~~> >= x.y && < x.(y+1) The "~" operator should be read as "in the range of". Another option would have been "-", but this is used to specify exact versions in other parts of the Cabal infrastructure , e.g., "cabal install xmonad-0.5". This is the most common specification of package dependencies. The assumption is that changes in the last version number indicate only backwards compatible changes, as is suggested in the new package versioning policy [1]. The use of "*" matches the common usage as a wildcard character. (2) Upward Ranges ~ 1.2.1+ ~~> >= 1.2.1 && < 1.3 in general ~ x.y.z+ ~~> >= x.y.z && < x.(y+1) The idea here is that sometimes packages need a certain patch level or, as in Cabal's case, a stable release and possible further bugfixes. In those cases the wildcard notation is too liberal, however the explicit range description would be too noisy (and possibly error prone). (Also, using "+" instead of "*" serves as better visual distinction.) We believe, that these kinds of ranges will become very common, thus justifying a syntactic extension. It also encourages specifying correct dependency descriptions, thus could increase the quality of packages on Hackage overall. It could be argued that 1.2.3+ could be misunderstood as > 1.2.3. However, if package authors start to adopt the new package versioning policy, this would actually Do The Right Thing (tm). / Thomas (& Duncan) [1] .. http://haskell.org/haskellwiki/Package_versioning_policy

2 1

patch applied (cabal): Fix warnings in Cabal
by Duncan Coutts 22 Jan '08

22 Jan '08

Fri Jan 18 11:12:30 PST 2008 Ian Lynagh <igloo(a)earth.li> UNDO: Fix warnings in Cabal M ./Distribution/Simple/Program.hs -4 +4

1 0

patch applied (cabal): Fixup breakage from previous changes
by Duncan Coutts 22 Jan '08

22 Jan '08

Mon Jan 21 14:07:43 PST 2008 Duncan Coutts <duncan(a)haskell.org> * Fixup breakage from previous changes M ./Distribution/Make.hs -1 +3 M ./Distribution/Simple/SetupWrapper.hs -2 +2

1 0

Re: [Hackage] #57: maybe: each new package uploaded to hackageDB should create a component in trac?
by Hackage 22 Jan '08

22 Jan '08

#57: maybe: each new package uploaded to hackageDB should create a component in trac? --------------------------------+------------------------------------------- Reporter: ijones | Owner: ijones Type: enhancement | Status: new Priority: normal | Milestone: _|_ Component: HackageDB website | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.2.1 | Platform: Linux --------------------------------+------------------------------------------- Changes (by duncan): * milestone: => _|_ Comment: Many packages use their own bug tracking system and will not want to change. Perhaps all we need is a url for bug reports. That might be the maintainer's email address or it might be a url to a web bug tracker. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/57#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #92: issues with 'clean'
by Hackage 22 Jan '08

22 Jan '08

#92: issues with 'clean' ----------------------------+----------------------------------------------- Reporter: simonmar | Owner: ijones Type: defect | Status: closed Priority: normal | Milestone: Cabal-1.2 Component: Cabal library | Version: 1.1.4 Severity: normal | Resolution: fixed Keywords: | Difficulty: very easy (<1 hour) Ghcversion: 6.4.2 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by duncan): * status: new => closed * resolution: => fixed Comment: As far as I know, all preprocessor output now goes under `dist/` and clean does not try to remove anything from the src dirs (except user-specified `extra-clean-files` and some jhc files that really ought to be put under `dist/` in the first place.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/92#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

patch applied (cabal): Fix --with-compiler / --with-hc inconsistency in ./configure flags
by Duncan Coutts 22 Jan '08

22 Jan '08

Mon Jan 21 10:29:48 PST 2008 Duncan Coutts <duncan(a)haskell.org> * Fix --with-compiler / --with-hc inconsistency in ./configure flags setup configure takes a --with-compiler option, but used to change that into a --with-hc option when calling ./configure. Now that we've added autoconfUserHooks and deprecated defaultUserHooks we can fix this without breaking any existing scripts. The autoconfUserHooks now passes --with-compiler to ./configure and defaultUserHooks is unchanged. Fixes ticket #114. M ./Distribution/Simple.hs -2 +5 M ./Distribution/Simple/Setup.hs -5 +9

1 0

patch applied (cabal): Move chattyTry into Utils module
by Duncan Coutts 22 Jan '08

22 Jan '08

Mon Jan 21 09:10:31 PST 2008 Duncan Coutts <duncan(a)haskell.org> * Move chattyTry into Utils module M ./Distribution/Simple.hs -11 +1 M ./Distribution/Simple/Utils.hs +10

1 0

Re: [Hackage] #39: add flag to sdist to include preprocessed sources?
by Hackage 22 Jan '08

22 Jan '08

#39: add flag to sdist to include preprocessed sources? ----------------------------+----------------------------------------------- Reporter: ijones | Owner: ijones Type: enhancement | Status: closed Priority: high | Milestone: Component: Cabal library | Version: Severity: normal | Resolution: fixed Keywords: | Difficulty: normal Ghcversion: 6.2.1 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by duncan): * status: new => closed * resolution: => fixed Comment: Mostly fixed now. `PreProcessor` does now know whether the output is OS-independent. The output from such preprocessors is automatically included into source tarballs (though in an unhelpful place see #166). I've not seen any demand for including the output of platform-dependent preprocessors, indeed that seems rather unwise in general. The issue about `build-tools` is still unresolved. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/39#comment:3> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #114: --with-compiler / --with-hc inconsistency
by Hackage 22 Jan '08

22 Jan '08

#114: --with-compiler / --with-hc inconsistency ----------------------------------+----------------------------------------- Reporter: ross(a)soi.city.ac.uk | Owner: ijones Type: enhancement | Status: closed Priority: high | Milestone: Component: Cabal library | Version: 1.1.6 Severity: normal | Resolution: fixed Keywords: | Difficulty: normal Ghcversion: 6.4.2 | Platform: Linux ----------------------------------+----------------------------------------- Changes (by duncan): * status: new => closed * resolution: => fixed Comment: `autoconfUserHooks` now uses "--with-compiler" and the old deprecated `defaultUserHooks` uses the same as before so existing scripts will not break. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/114#comment:2> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

Re: [Hackage] #58: allow darcs repo to be specified in cabal file
by Hackage 21 Jan '08

21 Jan '08

#58: allow darcs repo to be specified in cabal file ----------------------------+----------------------------------------------- Reporter: ijones | Owner: ijones Type: enhancement | Status: new Priority: high | Milestone: Cabal-1.4 Component: Cabal library | Version: Severity: normal | Resolution: Keywords: | Difficulty: normal Ghcversion: 6.2.1 | Platform: Linux ----------------------------+----------------------------------------------- Changes (by duncan): * component: HackageDB website => Cabal library * summary: darcs integration idea: track location of darcs repo, create new repo => allow darcs repo to be specified in cabal file Old description: > add a field to cabal to specify a darcs repo. if there's no such field, > create a darcs repo and make it available. accept patches against it and > forward them to upstream author, or just hang on to them New description: add a field to cabal to specify a darcs repo. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/58#comment:4> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0