[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: ghc 8
From: |
ng0 |
Subject: |
Re: ghc 8 |
Date: |
Mon, 05 Sep 2016 10:40:30 +0000 |
Ludovic Courtès <address@hidden> writes:
> ng0 <address@hidden> skribis:
>
>> should we package ghc 8 in core-updates? It was released in May:
>> https://ghc.haskell.org/trac/ghc/blog/ghc-8.0.1-released
>
> Probably a good idea. :-)
>
> This can be done in ‘master’, or, if we change to default GHC, to a
> dedicated ‘ghc-update’ branch.
>
> Ludo’.
Should this replace current ghc? I don't know how much of our current
(gnu packages haskell) would break.
For example we have this[0] bug for a current package[1] I am working
on.
Solution A would be to go multiversion, keep ghc7 around for all
packages which do not support ghc8 yet.
Solution B is just update the version and see what breaks on hydra build
of all of haskell.
I'll start this with solution B in a master-ghc8 branch to just take a
look at ghc8 build and see if something fails.
It's contraproductive to my haskell work, but I can't figure out at the
moment why darcs fails in the middle of the build.
[0]: http://bugs.darcs.net/issue2505
[1]: https://gitlab.com/packaging-guix/guix-darcs (mirror)
--
ng0
For non-prism friendly talk find me on http://www.psyced.org