From mboxrd@z Thu Jan  1 00:00:00 1970
From: ng0 <ng0@we.make.ritual.n0.is>
Subject: Re: ghc 8
Date: Wed, 07 Sep 2016 10:21:18 +0000
Message-ID: <8737lc9fj5.fsf@we.make.ritual.n0.is>
References: <87y437u61m.fsf@we.make.ritual.n0.is> <87a8fni9xp.fsf@gnu.org>
	<87bn02zl29.fsf@we.make.ritual.n0.is> <87r38woylf.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]:59255)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ng0@we.make.ritual.n0.is>) id 1bhZyv-0006gT-So
	for guix-devel@gnu.org; Wed, 07 Sep 2016 06:21:27 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ng0@we.make.ritual.n0.is>) id 1bhZyu-0002wY-LL
	for guix-devel@gnu.org; Wed, 07 Sep 2016 06:21:25 -0400
In-Reply-To: <87r38woylf.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:
>
>> 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