|Then, after adding "base < 4" to all extralibs .cabal files, I'm
|treated to a
|
|Network.hs:434:10:
| Couldn't match expected type `Exception.IOException'
| against inferred type `Exception.Exception'
| Expected type: Exception.IOException -> IO a
| Inferred type: Exception.Exception -> IO a
| In the expression: Exception.catch
| In the definition of `catchIO': catchIO = Exception.catch
That's because network's code requires base 4 due to this patch:
Make network work with extensible exceptions
Ian Lynagh <[EMAIL PROTECTED]>**20080805125755
Thanks, now we're finally getting somewhere!-)
So, that patch was incomplete and left the package
unbuildable, because the .cabal wasn't updated, right?
Presumably, the patch code should be under .cabal-configurations
generated CPP, so that both older and newer ghcs (with or without
base 4) can still build that package? Which means a .cabal flag,
similar to splitbase, in spite of the presence of base3-compat. Which
is one of the things you want to find out now, by building full heads,
with extralibs, not something you want to users to run into after the
ghc release.
And the workaround for me is not to specify base < 4, but
to guess which of the split-off former base packages are
build-depends for network, correct? And to guess which other
extralibs are in a similar state?
Claus
_______________________________________________
Cvs-ghc mailing list
Cvs-ghc@haskell.org
http://www.haskell.org/mailman/listinfo/cvs-ghc
