- cabal-devel - Haskell.org

patch applied (cabal): Tweak whitespace
by Ian Lynagh 29 Jul '08

29 Jul '08

Tue Jul 29 09:37:29 PDT 2008 Ian Lynagh <igloo(a)earth.li> * Tweak whitespace M ./Distribution/Simple/PreProcess.hs -1 +1 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080729163729-3fd76-a9a2418e…

1 0

[Hackage] #213: allow wildcards in data-files or extra-source-files?
by Hackage 29 Jul '08

29 Jul '08

#213: allow wildcards in data-files or extra-source-files? ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Some packages end up with very very long fields for data-files or extra- source-files. Is this a problem? Should we allow some kind of globing to make it a bit less verbose? {{{ extra-source-files: cbits/*.h c-sources: cbits/*.c }}} On the other hand, there is a danger with globing that you pick up too many files. Perhaps we can counter that by making the globing rather restrictive, like no subdirectory recursion, and only allowing *'s in the final directory component, so no {{{data/*/*}}} patterns. Is there a sweet spot that allows conciseness without including too much accidentally? -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/213> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 6

[Hackage] #295: ld-options parsing treats , as separator
by Hackage 29 Jul '08

29 Jul '08

#295: ld-options parsing treats , as separator ----------------------------+----------------------------------------------- Reporter: duncan | Owner: Type: defect | Status: new Priority: normal | Milestone: Cabal-1.4 Component: Cabal library | Version: HEAD Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Say we've got X11.buildinfo.in: {{{ ld-options: @X_LIBS@ @LDFLAGS@ }}} and imagine that someone has all kinds of crazy `LDFLAGS`: {{{ LDFLAGS="-Wl,-O1 -Wl,--sort-common -Wl,--hash-style=gnu -Wl,-z,relro -Wl ,--as-needed -Wl,-z,now" }}} Can you guess what happens? We end up parsing that as: {{{ ldOptions = ["-Wl", "-O1", "-Wl", "--sort-common", "-Wl", "--hash-style=gnu", "-Wl", "-z", "relro", "-Wl", "--as-needed", "-Wl", "-z", "now"] }}} This is because the parser for the `ld-options` field is defined using `listField` which uses `parseOptCommaList` which uses space and `','` as value separators. We should use just spaces for this field and also for `cc-options` and `cpp-options`. If we make this change we'll have to check that we're not going to break things for existing .cabal files that might use ',' as a separator. Will require an audit of .cabal files on hackage. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/295> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

[Hackage] #312: Multiple architectures under .cabal/
by Hackage 29 Jul '08

29 Jul '08

#312: Multiple architectures under .cabal/ ------------------------------+--------------------------------------------- Reporter: larsv | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: minor | Keywords: Difficulty: easy (<4 hours) | Ghcversion: 6.8.2 Platform: | ------------------------------+--------------------------------------------- Currently, the path in the home directory which cabal-install puts installed packages in does not contain the architecture in any way. This makes things bothersome for people who has the same ${HOME} on several different architectures. The proposed solution in #haskell is to "add ${arch} as a path template". -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/312> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 3

[Hackage] #232: implement extended syntax for package version ranges
by Hackage 29 Jul '08

29 Jul '08

#232: implement extended syntax for package version ranges ----------------------------+----------------------------------------------- Reporter: duncan | Owner: nominolo Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: 1.2.3.0 Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.2 Platform: | ----------------------------+----------------------------------------------- Revised proposal: http://www.haskell.org/pipermail/cabal- devel/2008-January/001786.html Reproduced here: 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. == 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. == 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.) -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/232> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 5

patch applied (cabal): Move docs for build-depends into the build information section
by Duncan Coutts 29 Jul '08

29 Jul '08

Tue Jul 29 09:20:24 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Move docs for build-depends into the build information section Since it is shared between libs and exes. Extend the documentation to describe the syntax of version constraints, including the new version range syntax "build-depends: foo ==1.2.*". M ./doc/Cabal.xml -27 +38 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080729162024-adfee-252d77c9…

1 0

patch applied (cabal): Remove references to cabal-setup from the documentation
by Duncan Coutts 29 Jul '08

29 Jul '08

Tue Jul 29 09:09:50 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Remove references to cabal-setup from the documentation Change to runhaskell Setup or cabal-install as appropriate. M ./doc/Cabal.xml -5 +4 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080729160950-adfee-fd7daee3…

1 0

patch applied (cabal): Move the docs for the buildable field to a better place.
by Duncan Coutts 29 Jul '08

29 Jul '08

Tue Jul 29 09:08:08 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Move the docs for the buildable field to a better place. It doesn't need to be right up near the top. M ./doc/Cabal.xml -14 +14 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080729160808-adfee-f4f65635…

1 0

patch applied (cabal): Document more clearly that every modules must be listed
by Duncan Coutts 29 Jul '08

29 Jul '08

Tue Jul 29 09:03:08 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Document more clearly that every modules must be listed in one of the fields exposed-modules, other-modules or main-is Add an extra note to the section on the Paths_pkgname module as the fact that it's automatically generated confuses people. M ./doc/Cabal.xml +19 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080729160308-adfee-2320e922…

1 0

patch applied (cabal): Document the wildcard behaviour in data-files and extra-source-files fields
by Duncan Coutts 29 Jul '08

29 Jul '08

Tue Jul 29 08:59:20 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Document the wildcard behaviour in data-files and extra-source-files fields M ./doc/Cabal.xml +26 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080729155920-adfee-011d48dc…

1 0