From: ng0 <ng0@we.make.ritual.n0.is>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: ghc 8
Date: Mon, 05 Sep 2016 10:40:30 +0000 [thread overview]
Message-ID: <87bn02zl29.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87a8fni9xp.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> ng0 <ng0@we.make.ritual.n0.is> 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
next prev parent reply other threads:[~2016-09-05 10:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-04 13:51 ghc 8 ng0
2016-09-04 22:20 ` Ludovic Courtès
2016-09-05 10:40 ` ng0 [this message]
2016-09-05 23:16 ` ng0
2016-09-07 9:20 ` Ludovic Courtès
2016-09-07 10:21 ` ng0
2016-09-26 20:54 ` ng0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn02zl29.fsf@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).