From: John Soo <jsoo1@asu.edu>
To: John Kehayias <john.kehayias@protonmail.com>,
Xinglu Chen <public@yoctocell.xyz>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Create branch for Haskell build changes and updates?
Date: Wed, 7 Jul 2021 08:02:29 -0700 [thread overview]
Message-ID: <8714eadc-379a-4b28-8a9b-044fc02ca9f4@Canary> (raw)
In-Reply-To: <EUwd6bBJqYUYCpshM_K390ReHY_uWwRp8sr2f49m1JubPbFxWVBKRoGbMoEz7IVNCfReB2Yadix_Xhme07Xy4_WppyL6t09AuwtCMoJkTq0=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 522 bytes --]
Hey Guix,
I’m very happy to see some movement on haskell support.
We try to track the stack package set for a given ghc version. Updating to ghc 8.10.4, then, means updating to stackage lts 18.1.
One other issue that should be addressed is that cabal-install will need to be updated to 3.x. I have tried but I don’t know how to build it.
I also nominate updating the ghc-profile-hook. It needs some work to be fully functional. Perhaps a search-path would be the way to go there?
Kindly,
John Soo
[-- Attachment #2: Type: text/html, Size: 1018 bytes --]
next prev parent reply other threads:[~2021-07-07 15:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-05 17:24 Create branch for Haskell build changes and updates? John Kehayias
2021-07-07 5:47 ` Xinglu Chen
2021-07-07 14:47 ` John Kehayias
2021-07-07 15:02 ` John Soo [this message]
2021-07-08 17:45 ` Xinglu Chen
2021-07-09 14:06 ` Ricardo Wurmus
2021-07-09 15:21 ` John Kehayias
2021-07-09 16:44 ` Ricardo Wurmus
2021-07-09 18:45 ` John Kehayias
2021-07-10 15:39 ` Xinglu Chen
2021-07-20 11:58 ` Philip Munksgaard
2021-07-20 16:49 ` Ricardo Wurmus
2021-07-20 19:41 ` Philip Munksgaard
2021-07-21 21:10 ` Ricardo Wurmus
2021-07-27 21:24 ` John Kehayias
2021-07-27 21:34 ` Ricardo Wurmus
2021-07-20 22:24 ` Ricardo Wurmus
2021-07-24 13:40 ` Xinglu Chen
2021-07-24 15:00 ` Ricardo Wurmus
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8714eadc-379a-4b28-8a9b-044fc02ca9f4@Canary \
--to=jsoo1@asu.edu \
--cc=guix-devel@gnu.org \
--cc=john.kehayias@protonmail.com \
--cc=public@yoctocell.xyz \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.