unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars-Dominik Braun <lars@6xq.net>
To: Xinglu Chen <public@yoctocell.xyz>
Cc: 49606@debbugs.gnu.org, Ricardo Wurmus <rekado@elephly.net>,
	Sarah Morgensen <iskarian@mgsn.dev>,
	John Kehayias <john.kehayias@protonmail.com>
Subject: [bug#49606] [PATCH wip-haskell v2] gnu: Add ghc-8.10.
Date: Tue, 14 Sep 2021 15:02:41 +0200	[thread overview]
Message-ID: <YUCdcbnf7izodWtN@noor.fritz.box> (raw)
In-Reply-To: <8735q8v4qp.fsf@yoctocell.xyz>

Hi,

> AFAIK, ‘-next’ packages are usually unstable versions of the regular
> version, e.g., ‘emacs-next’ and ‘guile-next’.  ‘ghc-8.10’ is a stable
> release, so I am not sure if the ‘-next’ prefix is appropriate.
that is true, but I don’t see any other way to make

	guix environment --pure --ad-hoc ghc ghc-aeson -- ghci
	> import Data.Aeson

do “the right thing” by default. We could also argue that from
Guix’s point of view GHC 8.8/8.10 is (right now) unstable, because our
entire set of Haskell packages is built with GHC 8.6 (and thus untested
with higher versions of base). We also have python-next@3.9.2 on master
with (I think) exactly the same purpose. So, unless there’s any strong
objections I’ll be bold and rename GHC>8.6 to ghc-next, explaining
the situation in a comment.

> But seeing as there isn’t much interest in a
> Haskell update, applying to ‘master’ seems like a better idea.
I’m counting three people (John, you and me) interested in getting
Haskell back into shape, so let’s just do it :)

Cheers,
Lars





  parent reply	other threads:[~2021-09-14 13:24 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-17 15:34 [bug#49606] [PATCH] gnu: Add ghc-8.10 Xinglu Chen
2021-07-17 19:24 ` Sarah Morgensen via Guix-patches via
2021-07-23 20:48   ` Xinglu Chen
2021-07-30 22:12 ` [bug#49606] [PATCH wip-haskell v2] " Xinglu Chen
2021-08-12 10:18   ` Xinglu Chen
2021-09-13 14:24     ` Lars-Dominik Braun
2021-09-13 16:07       ` Xinglu Chen
2021-09-13 16:55         ` John Kehayias via Guix-patches via
2021-09-14 13:02         ` Lars-Dominik Braun [this message]
2021-09-14 15:21           ` Xinglu Chen
2021-09-15  7:46             ` bug#49606: " Lars-Dominik Braun
2021-09-15 19:31               ` [bug#49606] " John Kehayias via Guix-patches via

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=YUCdcbnf7izodWtN@noor.fritz.box \
    --to=lars@6xq.net \
    --cc=49606@debbugs.gnu.org \
    --cc=iskarian@mgsn.dev \
    --cc=john.kehayias@protonmail.com \
    --cc=public@yoctocell.xyz \
    --cc=rekado@elephly.net \
    /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).