From mboxrd@z Thu Jan  1 00:00:00 1970
From: ng0 <ng0@we.make.ritual.n0.is>
Subject: Re: ghc 8
Date: Mon, 05 Sep 2016 10:40:30 +0000
Message-ID: <87bn02zl29.fsf@we.make.ritual.n0.is>
References: <87y437u61m.fsf@we.make.ritual.n0.is> <87a8fni9xp.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:49085)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ng0@we.make.ritual.n0.is>) id 1bgrKO-0005xz-Qz
	for guix-devel@gnu.org; Mon, 05 Sep 2016 06:40:37 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ng0@we.make.ritual.n0.is>) id 1bgrKL-0004sI-Ld
	for guix-devel@gnu.org; Mon, 05 Sep 2016 06:40:35 -0400
In-Reply-To: <87a8fni9xp.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@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