November 2008 - cabal-devel

patch applied (cabal): Simplify previous pkg-config fix
by Duncan Coutts 03 Nov '08

03 Nov '08

Sat Nov 1 13:03:09 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Simplify previous pkg-config fix M ./Distribution/Simple/Configure.hs -3 +3 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081101200309-adfee-7bfbef97…

1 0

Re: cabal
by Duncan Coutts 02 Nov '08

02 Nov '08

On Tue, 2008-10-21 at 10:51 +0200, Christian Maeder wrote: > So network-2.2.0.0 should be linked against base-3 within the binary > dist of ghc-6.10 (or not shipped with ghc-6.10 at all. > > In fact it worked after I've unregistered my global network-2.2.0.0, > first! (but I didn't get much further, see below) network-2.2.0.1 is now on hackage which should resolve the issue. > > Normally cabal-install would use base-3 but in this case it's picking 4 > > because the version that is already installed used 4 so the assumption > > is that since the same version is already installed then it does indeed > > work with base 4. Of course that's not true here because the package has > > changed without the version being bumped. > > Or cabal-install should be smarter (or less smart). Unfortunately it cannot be less smart or it'd try rebuilding haskell98 against base 3. > So why is the version of network not bumped, yet? The maintainer is > libraries(a)haskell.org. Would it interfere with ghc-6.8? Done, and it works with (at least) ghc-6.6.1, 6.8.2 and 6.10.0.recent. Duncan

1 0

patch applied (cabal): Fix bug where we'd try to configure an empty set of pkg-config packages
by Duncan Coutts 02 Nov '08

02 Nov '08

Sat Nov 1 12:55:12 PDT 2008 Duncan Coutts <duncan(a)haskell.org> * Fix bug where we'd try to configure an empty set of pkg-config packages This happened when the lib used pkg-config but the exe did not. It cropped up in hsSqlite3-0.0.5. M ./Distribution/Simple/Configure.hs -2 +3 View patch online: http://darcs.haskell.org/cabal/_darcs/patches/20081101195512-adfee-0233e9fa…

1 0

Re: darcs patch: Read the .cabal file as UTF8 when unpacking
by Ross Paterson 02 Nov '08

02 Nov '08

On Sat, Nov 01, 2008 at 03:30:24PM +0000, Duncan Coutts wrote: > Sat Nov 1 15:24:48 GMT 2008 Duncan Coutts <duncan(a)haskell.org> > * Read the .cabal file as UTF8 when unpacking > Currently the upload check preview displays incorrect encoding of > peoples names and does not validate incorrect UTF8 encodings. > This should fix it, though not actually tested. Applied, thanks.

1 0

[Hackage] #388: Add a warning for unknown modules that were compiled
by Hackage 02 Nov '08

02 Nov '08

#388: Add a warning for unknown modules that were compiled ----------------------------+----------------------------------------------- Reporter: jcpetruzza | Owner: Type: enhancement | Status: new Priority: normal | Milestone: Component: Cabal library | Version: Severity: normal | Keywords: Difficulty: normal | Ghcversion: 6.8.3 Platform: | ----------------------------+----------------------------------------------- Let's say you are working on a new version of a library; you add a new internal (i.e. non-exposed) module but you forget to update the package description. You locally test your changes, everything works fine so you install it. Now, since the new module is not listed in {{{other-modules}}} it will not be included in the final library. Therefore, when you try to use it you get rather cryptic linker errors. It can take a while until you realize where the problem is coming from. The proposal is to look, during build, for compiled modules under the {{{dist}}} directory that are not included in the final library and warn the user about their presence. -- Ticket URL: <http://hackage.haskell.org/trac/hackage/ticket/388> Hackage <http://haskell.org/cabal/> Hackage: Cabal and related projects

1 1

darcs patch: Read the .cabal file as UTF8 when unpacking
by Duncan Coutts 01 Nov '08

01 Nov '08

Sat Nov 1 15:24:48 GMT 2008 Duncan Coutts <duncan(a)haskell.org> * Read the .cabal file as UTF8 when unpacking Currently the upload check preview displays incorrect encoding of peoples names and does not validate incorrect UTF8 encodings. This should fix it, though not actually tested.

1 0