Should we aim for a new release in late January?
simonpj at microsoft.com
Thu Nov 28 11:41:51 UTC 2013
I'm thrilled that there so much Cabal activity!
Is anyone working on, or interested in, the issue of compiling and installing the same package against different dependencies? (There was a Google SoC project about this.) Cabal sandboxes address the same issue, but at some user cost. It should Just Work.
From: cabal-devel [mailto:cabal-devel-bounces at haskell.org] On Behalf Of Johan Tibell
Sent: 27 November 2013 21:01
To: cabal-devel at haskell.org
Subject: Should we aim for a new release in late January?
Cabal development is continuing at a furious pace. There are lots of great things in master that I'd like to get out to users, such as
* relinking avoidance
* build -j
* ability to specify exact deps on the command line
* haskell-suite compiler support
* bug fixes
Here's an approximate list of commits (both Cabal and cabal-install) since the last release:
It's not entirely accurate as some patches were cherry-picked onto the 1.18 branch and thus have different commit IDs.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cabal-devel