all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Xinglu Chen <public@yoctocell.xyz>
To: John Kehayias <john.kehayias@protonmail.com>,
	"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Create branch for Haskell build changes and updates?
Date: Wed, 07 Jul 2021 07:47:44 +0200	[thread overview]
Message-ID: <8735sqisjj.fsf@yoctocell.xyz> (raw)
In-Reply-To: <e7BRZzcL_m4HQVFynEoJhiwl7-MNGGeVEXrXExHAjPuEl9KtiGsySm7YY5sQ4evmx_O3V1mhFq_p3PafWbCKy9t5_0gfR2I2IJCmV8JTryY=@protonmail.com>

[-- Attachment #1: Type: text/plain, Size: 2255 bytes --]

On Mon, Jul 05 2021, John Kehayias wrote:

> Hello,
>
> There have been several recent bug reports and patches (list below)
> that could be addressed with some changes to haskell-build-system, the
> Hackage importer, and some package updates. Given the number of
> packages affected, it was discussed on #guix that it would be good to
> have a branch for these changes and to have Cuirass build the Haskell
> packages to look for breakage.
>
> How do we feel about this? I'm happy to help with some patches I've
> submitted and update some packages, though it would also be good to
> have someone experienced with Haskell packaging and/or Guix too. (I'm
> new to both, but I've had success with my patches at least, locally.)
>
> Here is a (partial) list of the most recent bugs and patches that
> would belong on this branch:
>
> - https://issues.guix.gnu.org/48944 (build failure for new package,
>   addressed by next patch)
>
> - https://issues.guix.gnu.org/49199 (patch to add package-db to
>   runhaskell to help with non-trivial configure stage; worked around in
>   existing packages with a TODO marked to make this change actually)
>
> - https://issues.guix.gnu.org/49418 (metadata revisions not imported,
>   so e.g. dependency requirements out of date)
>
> - https://issues.guix.gnu.org/49326 (bug with specifying ghc version
>   for building)
>
> - https://issues.guix.gnu.org/49320 (importer doesn't support some
>   stages)
>
> - https://issues.guix.gnu.org/48999 (local source for Haskell
>   packages)
>
> I'm not sure what we would want to include or not in such a branch,
> but I think it would make sense to put together the build-system and
> related changes at least. Some package updates (like a ghc version)
> would also affect a lot of packages, so might be good to do that
> together as well.

Thank you for bringing this up!  I posted a WIP patch for adding GHC
8.10 a while ago, but nobody showed any interest[1].

I don’t have any experience with updating the Haskell toolchain in Guix,
but I think it would be great to have a separate branch for updating the
haskell-build-system and Haskell packages.  :)

[1]: https://yhetil.org/guix-devel/87o8cgfbg1.fsf@yoctocell.xyz/

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]

  reply	other threads:[~2021-07-07  5:48 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 [this message]
2021-07-07 14:47   ` John Kehayias
2021-07-07 15:02     ` John Soo
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=8735sqisjj.fsf@yoctocell.xyz \
    --to=public@yoctocell.xyz \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.com \
    /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.