On Wed, Jul 11, 2007 at 06:01:59AM +0200, Marc Weber wrote:
> The following packages (not including those which I couldn't build yet
> because I han't add missing C dependencies etc) are broken:
>
> log-hackage-BerkeleyDB-0.2:Couldn't match expected type `CInt' against
> inferred type `CMode'
We *really* need to start testing API divergences against hackage
packages, before GHC releases.
marco-oweber:
> The following packages (not including those which I couldn't build yet
> because I han't add missing C dependencies etc) are broken:
>
> log-hackage-BerkeleyDB-0.2:Couldn't match
The following packages (not including those which I couldn't build yet
because I han't add missing C dependencies etc) are broken:
log-hackage-BerkeleyDB-0.2:Couldn't match expected type `CInt' against
inferred type `CMode'
log-hackage-FileManip-0.2:Couldn't match expected type `CInt' aga
The following packages are listed more than once:
"Crypto"
"GuiTV"
"TypeCompose"
"Win32"
"binary"
"polyparse"
That's not by accident, is it?
___
cabal-devel mailing list
cabal-devel@haskell.org
http://www.haskell.org/mailman/listinfo/cabal-devel
On Tue, 2007-07-10 at 13:19 -0500, [EMAIL PROTECTED] wrote:
> Tue Jul 10 13:13:42 CDT 2007 Spencer Janssen <[EMAIL PROTECTED]>
> * Add modules to cabal-setup.cabal: this makes Setup sdist work
Ta. Applied.
Duncan
___
cabal-devel mailing list
cabal-d
Tue Jul 10 13:13:42 CDT 2007 Spencer Janssen <[EMAIL PROTECTED]>
* Add modules to cabal-setup.cabal: this makes Setup sdist work
New patches:
[Add modules to cabal-setup.cabal: this makes Setup sdist work
Spencer Janssen <[EMAIL PROTECTED]>**20070710181342] {
hunk ./cabal-install.cabal 19
+Ext
I'm packaging all hackage packages for nix. I've already compiled 102
packages succesfully.
Is there a simple way to do a
./setup haddock --dirs-containing-dep-docs=path1;path2;path3;path4 ..
--install-to $out/haddock ?
If not who is working on haddock stuff right now?
Marc
...would you please review this patch? ;-)
Sorry if I am being too pushy, but I'd want to avoid people developing
on the "old" Haddock integration code (assuming this patch is worth
inclusion, of course).
Zun.
=
I am sending a patch[1] for integrating Cabal and HsColour + Haddock.
Here
Hi
When installing a .cabal package which has Windows line endings, the
executable name is read as file^M. There are a few possible solutions:
1) Ban \r from .cabal files - cabal-upload should check this if this
choice is made.
2) Cope with \r, a simple filter (/= '\r') should be sufficient.
T
