> We've been saying all along though that the right thing to do is to
> switch the repo to the correct one. The other solutions were just ways
> of trying to avoid that.
I have only just realised that nhc98 was also using the broken ghc fork
of the bytestring library. Having corrected that, I now see that the
"one true" bytestring needs a few patches to build cleanly with nhc98
again. They are mostly to do with import-renaming bugs in nhc98.
Should I just push them to the repo, or would you like to review them
first? (I am unable to test locally because the bytestring tests do not
build cleanly for me either!)
Regards,
Malcolm
_______________________________________________
Cvs-libraries mailing list
[email protected]
http://www.haskell.org/mailman/listinfo/cvs-libraries
