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: Wed, 07 Sep 2016 10:21:18 +0000 [thread overview]
Message-ID: <8737lc9fj5.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87r38woylf.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> ng0 <ng0@we.make.ritual.n0.is> skribis:
>
>> 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.
>
> No idea. I suppose we take this route:
>
> 1. First you test a sample of ghc-* packages and build them to see if
> there’s obvious breakage.
>
> 2. If not, we commit the GHC upgrade in a branch and let Hydra build
> the branch.
>
> 3. We fix package breaks that we notice on the branch.
>
> 4. Merge the branch.
>
> How does that sound?
>
> Ludo’.
Sounds good to me.
--
ng0
For non-prism friendly talk find me on http://www.psyced.org
next prev parent reply other threads:[~2016-09-07 10:21 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
2016-09-05 23:16 ` ng0
2016-09-07 9:20 ` Ludovic Courtès
2016-09-07 10:21 ` ng0 [this message]
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=8737lc9fj5.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).