What do you think about Cabal?
Cabal 1.16.0 shiped with GHC 7.6.2. But latest Cabal version is 1.16.0.3, and
Cabal 1.16.0.3 has some bug fixes.
* http://www.haskell.org/ghc/docs/7.6.2/html/libraries/Cabal-1.16.0/index.html
* http://hackage.haskell.org/package/Cabal-1.16.0.3
* http://www.haskell.org/pipermail/haskell-cafe/2012-October/103746.html
* http://www.haskell.org/pipermail/haskell-cafe/2012-October/104099.html
Best Regards,
On Mon, 11 Mar 2013 00:06:36 +0900, Mark Lentczner <mark.lentcz...@gmail.com>
wrote:
I'd be pretty reluctant to either ship two versions of a GHC boot package,
or rebuild a GHC release with a different boot package version, in the HP.
Either would create a situation which I don't think any of us would be
confident is stable or a "sure thing". The first would create a really bad
"cabal-hell" trap (which is really a version constraint hell, not sure why
cabal takes the fall...). The second would lead to a situation where a bug
down the road would be come a tar-ball (in the bad sense) to unravel and
fix.
This is perhaps a good moment to reiterate that Haskell Platform exists to
create a clear, stable, "it just works", and "you can count on it"
distribution - and so by construction does not generally contain the latest
hotness.
- Mark
On Sun, Mar 10, 2013 at 6:54 AM, Gregory Collins <g...@gregorycollins.net>wrote:
On Sun, Mar 10, 2013 at 9:06 AM, Lennart Kolmodin <kolmo...@gmail.com>wrote:
Hi all,
binary just had a major upgrade and version 0.7 was released, covering a
few but very useful features. blog post
here<http://lennartkolmodin.blogspot.ru/2013/03/binary-07.html>
.
binary is bundled with GHC, so GHC 7.8 will upgrade to this new version
of binary.
GHC 7.6.2 however was released with the older binary 0.5.1.1.
The next HP, 2013.2.0.0, will use GHC 7.6.2 as I understand it, therefore
the old version of binary.
The HP will eventually upgrade to a more recent version of binary when it
will use GHC 7.8 or later.
My question is whether HP would like to upgrade before that happens.
Two approaches could be taken.
1. Add binary-0.7. There will be two versions of binary in HP.
2. Replace binary-0.5.1.1 with binary-0.7 in the source of GHC 7.6.2.
Requires a little bit of work, but the installers for HP would install only
one version of binary. However, distros who want to support the HP might
install GHC 7.6.2 first and then all packages, meaning that they would end
up with two versions of binary anyway (i.e. approach (1) above).
What do you think? Upgrade or wait until the new binary naturally gets
into the HP through a new GHC version? If upgrade, which approach?
Will the HP after the upcoming one use GHC 7.8? In that case it might
only be 6 months more wait and it'd resolve itself naturally.
I think for GHC boot packages we should ship with the same version that
ships with GHC.
--
Gregory Collins <g...@gregorycollins.net>
_______________________________________________
Haskell-platform mailing list
Haskell-platform@projects.haskell.org
http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
--
shelarcy <shelarcy hotmail.co.jp>
http://page.freett.com/shelarcy/
_______________________________________________
Haskell-platform mailing list
Haskell-platform@projects.haskell.org
http://projects.haskell.org/cgi-bin/mailman/listinfo/haskell-platform
