
Welcome to the cabal-devel mailing list! I'm very please to see so many folks signed up already. I'll just re-post the release announcement that Duncan made below. As Duncan mentioned, he'll be the release manager for Cabal, so hopefully I'll have a bit more time for hacking. All your donations will still go to me, though ;) peace, isaac === Cabal 1.1.4 release === Cabal-1.1.4, the version shipped with GHC 6.4.2 is now available to download as a separate tarball: http://haskell.org/cabal/download.html http://haskell.org/cabal/release/cabal-1.1.4/cabal-1.1.4.tar.gz Note that there was some confusion over the version number. If you got a darcs development snapshot in the last few months it will likely have been marked 1.1.4, however it should have been marked 1.1.5. 1.1.4 is the version shipped with GHC 6.4.2 and available as the tarball above. The current darcs development version is 1.1.5. We'll try to avoid such confusion in the future. === New Cabal-devel mailing list === There is also a new cabal-devel@haskell.org mailing list for Cabal development discussion including patch review. This is where patches sent via "darcs send" will end up. We welcome anyone to join the list and help discuss ongoing Cabal development or just to keep an eye on what's going in. Sign up here: http://haskell.org/mailman/listinfo/cabal-devel We'd also like to take the opportunity to invite people to get involved in Cabal development, either new features or squashing annoying bugs. It's as simple as: darcs get --partial http://darcs.haskell.org/packages/Cabal # write patch darcs record darcs send People who already commit directly via darcs push are welcome to continue to do so for patches they consider obvious. If they would like some review and feedback then they are welcome to "darcs send" instead and discuss the patch on the mailing list before committing. Note that this new list is not intended to take discussions of Cabal away from the libraries list. Issues affecting users should still go to libraries@haskell.org. The intention is to have more discussion and review of Cabal development. Duncan (who is wearing his new Cabal release manager's hat)

Isaac Jones
Welcome to the cabal-devel mailing list! I'm very please to see so many folks signed up already. I'll just re-post the release announcement that Duncan made below.
I've been hacking on minimizing the cabal-get requirements. I spoke to Bjorn Bringert, he split Network.Browser into its own package so that the Network.HTTP package no longer requires crypto. Next steps for me are to minimize xml-rpc and its dependency, HaXml. Anyone else hacking on Cabal? -- I've tried to teach people autodidactism, | ScannedInAvian.com but it seems they always have to learn it for themselves.| Shae Matijs Erisson

On 5/2/06, Shae Matijs Erisson
Isaac Jones
writes: Welcome to the cabal-devel mailing list! I'm very please to see so many folks signed up already. I'll just re-post the release announcement that Duncan made below.
I've been hacking on minimizing the cabal-get requirements. I spoke to Bjorn Bringert, he split Network.Browser into its own package so that the Network.HTTP package no longer requires crypto.
Next steps for me are to minimize xml-rpc and its dependency, HaXml.
Why not cut the xml-rpc dependency completely? It should be an evening hack to replace it with, say, BEncode. -- Friendly, Lemmih

Lemmih
On 5/2/06, Shae Matijs Erisson
wrote: Isaac Jones
writes: Welcome to the cabal-devel mailing list! I'm very please to see so many folks signed up already. I'll just re-post the release announcement that Duncan made below.
I've been hacking on minimizing the cabal-get requirements. I spoke to Bjorn Bringert, he split Network.Browser into its own package so that the Network.HTTP package no longer requires crypto.
Next steps for me are to minimize xml-rpc and its dependency, HaXml.
Why not cut the xml-rpc dependency completely? It should be an evening hack to replace it with, say, BEncode.
Shae also suggested getting rid of xml-rpc. I'm not totally against it, but it would be nice if folks could easily write clients! having a hackage-client packages is helpful here, but it doesn't help for other languages. Suggestions? peace, isaac

On 5/4/06, Isaac Jones
Lemmih
writes: On 5/2/06, Shae Matijs Erisson
wrote: Isaac Jones
writes: Welcome to the cabal-devel mailing list! I'm very please to see so many folks signed up already. I'll just re-post the release announcement that Duncan made below.
I've been hacking on minimizing the cabal-get requirements. I spoke to Bjorn Bringert, he split Network.Browser into its own package so that the Network.HTTP package no longer requires crypto.
Next steps for me are to minimize xml-rpc and its dependency, HaXml.
Why not cut the xml-rpc dependency completely? It should be an evening hack to replace it with, say, BEncode.
Shae also suggested getting rid of xml-rpc. I'm not totally against it, but it would be nice if folks could easily write clients! having a hackage-client packages is helpful here, but it doesn't help for other languages. Suggestions?
Writing a BEncode parser is almost simpler than learning to use an XML-toolkit. Jokes aside, I think our convenience is paramount and inter-language integration should be secondary. If we can get this thing in the air then by all means lets do it and leave these issues to a later version. -- Friendly, Lemmih

Lemmih
Shae also suggested getting rid of xml-rpc. I'm not totally against it, but it would be nice if folks could easily write clients! having a hackage-client packages is helpful here, but it doesn't help for other languages. Suggestions? Writing a BEncode parser is almost simpler than learning to use an XML-toolkit. Jokes aside, I think our convenience is paramount and inter-language integration should be secondary. If we can get this thing in the air then by all means lets do it and leave these issues to a later version.
I asked Isaac about this on irc, he said that xmlrpc keeps the complexity on the server. That way computing dependencies, efficient lookup over large sets, etc only depends on the clients knowing the names to call. I asked Isaac how cabal-get compared to apt (Isaac wrote part of apt-secure), he said that apt servers are simple but the client is extremely complex. Because of that there is only one client, and there likely won't be more. Isaac said he'd rather see simple clients and a complex server. Anyway, I think we should just 'get it in the air' as Lemmih put it. -- I've tried to teach people autodidactism, | ScannedInAvian.com but it seems they always have to learn it for themselves.| Shae Matijs Erisson
participants (3)
-
Isaac Jones
-
Lemmih
-
Shae Matijs Erisson