The current dilemma we're facing with the 6.12.1 release is this: cabal-install still needs to be ported to the new version of Cabal, Duncan is snowed under and doesn't have time to work on it, but without cabal-install people can't easily test 6.12.1 RC and we can't test it with Hackage. We've come to rely on cabal-install quite a lot. So, one option is just to release 6.12.1 as is, with the caveat that cabal-install doesn't work, and large portions of Hackage probably do not work (but we don't know what exactly). The platform isn't due to release with GHC 6.12.x until February 2010, and by then we could make a 6.12.2 to fix any problems that we discover when cabal-install is working. One potential problem is that having made the 6.12.1 release we wouldn't be able to make any further API changes, only bug fixes. Or, we could just make a 6.12.1 RC2, and advertise it with the same caveats, putting out 6.12.1 when cabal-install works and we've had a chance to see the state of Hackage and alert package authors. Simon and I favour the RC2 option. What do others think? Cheers, Simon
Simon Marlow wrote:
The current dilemma we're facing with the 6.12.1 release is this: cabal-install still needs to be ported to the new version of Cabal, Duncan is snowed under and doesn't have time to work on it, but without cabal-install people can't easily test 6.12.1 RC and we can't test it with Hackage. We've come to rely on cabal-install quite a lot.
Do we know how hard it is to make it work?
Simon and I favour the RC2 option. What do others think?
+1 Ganesh =============================================================================== Please access the attached hyperlink for an important electronic communications disclaimer: http://www.credit-suisse.com/legal/en/disclaimer_email_ib.html ===============================================================================
Simon Marlow schrieb:
Simon and I favour the RC2 option. What do others think?
+1 I've quite some trouble to port our old code to ghc-6.12 and did not test RC1 much. http://trac.informatik.uni-bremen.de:8080/hets/ticket/749 http://www.informatik.uni-bremen.de/htk/ Cheers Christian
On 22/10/2009 11:09, Christian Maeder wrote:
Simon Marlow schrieb:
Simon and I favour the RC2 option. What do others think?
+1
I've quite some trouble to port our old code to ghc-6.12 and did not test RC1 much.
http://trac.informatik.uni-bremen.de:8080/hets/ticket/749 http://www.informatik.uni-bremen.de/htk/
If you just need hPutBuf and hGetBuf, then get them from System.IO. Cheers, Simon
Simon Marlow schrieb:
On 22/10/2009 11:09, Christian Maeder wrote:
Simon Marlow schrieb:
Simon and I favour the RC2 option. What do others think?
+1
I've quite some trouble to port our old code to ghc-6.12 and did not test RC1 much.
http://trac.informatik.uni-bremen.de:8080/hets/ticket/749 http://www.informatik.uni-bremen.de/htk/
If you just need hPutBuf and hGetBuf, then get them from System.IO.
Thanks for this hint. I got further (also after replacing some non-ascii characters in comments, i.e. a broken bar "-- ¦ ..."). The next spot is: Posixutil/CopyFile.hs:124:19: Not in scope: `slurpFile' copyFileToCStringLen :: FilePath -> IO CStringLen copyFileToCStringLen file = do (ptr,len) <- slurpFile file return (castPtr ptr,len) Cheers Christian
On 22/10/2009 13:05, Christian Maeder wrote:
Simon Marlow schrieb:
On 22/10/2009 11:09, Christian Maeder wrote:
Simon Marlow schrieb:
Simon and I favour the RC2 option. What do others think?
+1
I've quite some trouble to port our old code to ghc-6.12 and did not test RC1 much.
http://trac.informatik.uni-bremen.de:8080/hets/ticket/749 http://www.informatik.uni-bremen.de/htk/
If you just need hPutBuf and hGetBuf, then get them from System.IO.
Thanks for this hint. I got further (also after replacing some non-ascii characters in comments, i.e. a broken bar "-- ¦ ..."). The next spot is:
Posixutil/CopyFile.hs:124:19: Not in scope: `slurpFile'
copyFileToCStringLen :: FilePath -> IO CStringLen copyFileToCStringLen file = do (ptr,len)<- slurpFile file return (castPtr ptr,len)
slurpFile was an internal operation in the IO library that went away. You should probably use ByteString's readFile instead. Cheers, Simon
At Thu, 22 Oct 2009 10:15:26 +0100, Simon Marlow wrote:
The current dilemma we're facing with the 6.12.1 release is this: cabal-install still needs to be ported to the new version of Cabal, Duncan is snowed under and doesn't have time to work on it, but without cabal-install people can't easily test 6.12.1 RC and we can't test it with Hackage. We've come to rely on cabal-install quite a lot.
Agreed. I've actually now got cabal-install building successfully locally on ghc 6.12 rc1, but it dies with "cabal: Prelude.undefined". I'm attempting to debug this now. So hopefully it shouldn't be too long before I/we get it working. -- Robin
Simon Marlow:
Or, we could just make a 6.12.1 RC2, and advertise it with the same caveats, putting out 6.12.1 when cabal-install works and we've had a chance to see the state of Hackage and alert package authors.
Simon and I favour the RC2 option. What do others think?
I agree. I don't think anybody benefits from an earlier, but buggier release. Manuel
participants (7)
-
Christian Maeder -
Manuel M T Chakravarty -
Niklas Broberg -
Robin Green -
Simon Marlow -
Sittampalam, Ganesh -
Troels Henriksen