- cabal-devel - Haskell.org

patch applied (cabal): Specify a source repository for Cabal in Cabal.cabal
by Duncan Coutts 01 Oct '08

01 Oct '08

Tue Sep 30 20:43:25 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Specify a source repository for Cabal in Cabal.cabal M ./Cabal.cabal +4 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081001034325-adfee-3ad2f7a3…

1 0

patch applied (cabal): Document the source-repository stuff
by Duncan Coutts 01 Oct '08

01 Oct '08

Tue Sep 30 20:39:28 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Document the source-repository stuff M ./doc/Cabal.xml -2 +189 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081001033928-adfee-725e06b5…

1 0

patch applied (cabal): Add some checks on the repository sections
by Duncan Coutts 01 Oct '08

01 Oct '08

Tue Sep 30 20:37:55 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Add some checks on the repository sections M ./Distribution/PackageDescription/Check.hs -1 +39 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081001033755-adfee-b94eec3b…

1 0

patch applied (cabal): Use unknown rather than specific other repo kinds
by Duncan Coutts 01 Oct '08

01 Oct '08

Tue Sep 30 20:36:37 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Use unknown rather than specific other repo kinds We can still add more as necessary M ./Distribution/PackageDescription.hs -8 +5 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081001033637-adfee-7c42a7f4…

1 0

patch applied (cabal): Add support for specifying source repos in .cabal files
by Duncan Coutts 01 Oct '08

01 Oct '08

Tue Sep 30 15:27:08 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Add support for specifying source repos in .cabal files Ticket #58. Does not yet include checking. M ./Distribution/PackageDescription.hs -6 +143 M ./Distribution/PackageDescription/Parse.hs -11 +62 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080930222708-adfee-5ad97a63…

1 0

patch applied (cabal): Simplify parsing sections in the .cabal file
by Duncan Coutts 01 Oct '08

01 Oct '08

Tue Sep 30 14:55:09 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Simplify parsing sections in the .cabal file Allow flags, lib and exes in any order and handle unknown sections better. M ./Distribution/PackageDescription/Parse.hs -67 +46 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080930215509-adfee-689acebf…

1 0

patch applied (cabal): Treat "cabal --flag command" as "cabal command --flag"
by Duncan Coutts 01 Oct '08

01 Oct '08

Sun Sep 28 00:06:27 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Treat "cabal --flag command" as "cabal command --flag" eg "cabal -v configure" to mean "cabal configure -v" For flags that are not recognised as global flags, pass them on to the sub-command. M ./Distribution/GetOpt.hs -1 +1 M ./Distribution/Simple/Command.hs -11 +20 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20080928070627-adfee-9a3bca71…

1 0

[Hackage] #364: cabal should allow source to be installed with/added to binary packages
by Hackage 29 Sep '08

29 Sep '08

#364: cabal should allow source to be installed with/added to binary packages ----------------------------+----------------------------------------------- Reporter: claus | 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: | ----------------------------+----------------------------------------------- We have the odd situation that package sources are used for `configure`/`build`/`haddock`/`install`/.., but aren't actually managed by cabal. This makes rebuilds (eg,with different options, or for another compiler version) or reinstalls (eg, with added or modified haddocks) somewhat chancey. Unless you keep your sources in a safe place, and remember where that was, you have to start by getting the sources again. (I assume that `cabal-install` has a cache of package source tarballs somewhere, but that doesn't account for modified-before-build-and-install package sources, right?) This is also an issue for source code analysis tools, if binary versions of imported packages aren't sufficient for processing the importing source. Haddock currently works around that by (a) being integrated with cabal and (b) generating its own interface files for installed packages (`*.haddock`); but we cannot expect all tools to be integrated with cabal. If tools and users could get programatic access to the sources that were used to install a package, they could refer to those for further processing. It is slightly ridiculous that the sources may be available in html-ized form (if haddock was used with appropriate options) but not in source form. See also: http://hackage.haskell.org/trac/ghc/ticket/2630 -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/364> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 0

darcs patch: don't try to find Paths_$pkg module when creating sdist
by jeanphilippe.bernardy＠gmail.com 29 Sep '08

29 Sep '08

Mon Sep 29 13:24:05 CEST 2008 jeanphilippe.bernardy(a)gmail.com * don't try to find Paths_$pkg module when creating sdist

1 0

Carriage returns in a .cabal file
by Clifford Beshers 28 Sep '08

28 Sep '08

The stb-image package on hackage has carriage returns (^M) at the end of some lines. This confused hlibrary.mk from the Debian haskell-devscripts. Are these characters legal in a .cabal file? I haven't found any mention of valid line terminators. If not, then I'll work with the author of stb-image, otherwise I'll fix the Debian tool.

2 1