From: zimoun <zimon.toutoune@gmail.com>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: rekado@elephly.net, Philip Munksgaard <philip@munksgaard.me>,
54729@debbugs.gnu.org
Subject: [bug#54729] [PATCH] build: haskell-build-system: Support packages w. multiple libraries
Date: Thu, 07 Apr 2022 09:35:39 +0200 [thread overview]
Message-ID: <86k0c14a7o.fsf@gmail.com> (raw)
In-Reply-To: <Yk5/xeYW4K4yDnLJ@noor.fritz.box>
Hi Lars,
On Thu, 07 Apr 2022 at 08:08, Lars-Dominik Braun <lars@6xq.net> wrote:
> I’d rather have this in a separate wip-haskell branch than let it sit
> on core-updates indefinitely. Stackage also has a new release[1] using
> GHC 9.0, which we could update to at the same time.
>
> Any other Haskell changes we can batch into that branch?
Ok, let’s do use this wip-haskell branch: fix the build system as this
v2 is doing and update LTS. Currently, the wip-haskell is at:
c1522b280137df2f670f47fa1e682e610406bb39 (Thu Sep 30 09:29:51 2021
+0200), so let me know once you have rebase it to the current master.
Cheers,
simon
next prev parent reply other threads:[~2022-04-07 7:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-05 15:15 [bug#54729] [PATCH] build: haskell-build-system: Support packages w. multiple libraries Philip Munksgaard
2022-04-06 19:19 ` [bug#54729] [PATCH core-updates v2 1/2] build: haskell-build-system: Remove trailing #t zimoun
2022-04-06 19:19 ` [bug#54729] [PATCH core-updates v2 2/2] build: haskell-build-system: Support multiple libraries zimoun
2022-04-06 19:23 ` [bug#54729] [PATCH] build: haskell-build-system: Support packages w. " zimoun
2022-04-07 6:08 ` Lars-Dominik Braun
2022-04-07 6:49 ` Philip Munksgaard
2022-04-07 8:25 ` Philip Munksgaard
2022-04-07 7:35 ` zimoun [this message]
2022-04-13 18:59 ` Philip Munksgaard
2022-04-14 18:21 ` Lars-Dominik Braun
2022-04-15 8:19 ` Philip Munksgaard
2022-09-23 9:42 ` itd
2022-12-21 12:48 ` itd
2022-12-23 14:03 ` Philip Munksgaard
2023-01-06 11:51 ` Lars-Dominik Braun
2023-01-12 17:30 ` itd
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=86k0c14a7o.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=54729@debbugs.gnu.org \
--cc=lars@6xq.net \
--cc=philip@munksgaard.me \
--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).