unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Saku Laesvuori <saku@laesvuori.fi>
To: Divya <divya@subvertising.org>
Cc: guix-devel@gnu.org
Subject: Re: Haskell & Rust Team on recent stable releases of compilers
Date: Mon, 21 Oct 2024 18:07:31 +0300	[thread overview]
Message-ID: <pjncwz422naeegjafzaepmoblpwtgnqm32hgml4tkqepqqswao@mws3a62ryann> (raw)
In-Reply-To: <792C5AC3-5268-4073-8EF4-D88C1EDCE072@subvertising.org>

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

> Hello Guix Devs,
> 
> I've been using Guix for the last few months. As a Haskell programmer,
> I realized the latest stable that's available in the guix package
> repository is 9.2.8 which is _really_ old, considering that the
> current stable releases are at least older than 9.6.x.
> 
> I'd like to contribute to this if I can, since I myself would like to
> have the latest GHC for my uses.  So, how can I get the latest
> versions available? Do I need to add every release, or can I just add
> the most latest?

I think you need to add every other major release to the chain. We
already have 9.2 and 9.4, so 9.6 should not be a problem in that regard.

> Also, is the process of adding a GHC release, or any Haskell package
> any different from the typical procedure to add a package? I'd like
> some introductory guidance/resources to learn that.

Not really, but this specific update (GHC 9.4 to 9.6) is quite tricky
because GHC changed their build system from a make to Hadrian. Hadrian
written in Haskell and depends on quite many packages, so we need to
build all those with an earlier GHC version to be able to build the
current GHC. See https://issues.guix.gnu.org/67921 for the current
situation with this. I am still quite busy with other things in life, so
feel free to pick those patches up.

The Guix manual[1] and cookbook[2] have generic documentation and examples
for creating Guix packages.

[1]: https://guix.gnu.org/manual/devel/en/guix.html
[2]: https://guix.gnu.org/cookbook/en/guix-cookbook.html

- Saku

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

  parent reply	other threads:[~2024-10-21 15:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21 14:50 Haskell & Rust Team on recent stable releases of compilers Divya
2024-10-21 14:57 ` Andreas Enge
2024-10-21 15:28   ` Divya Ranjan
2024-10-21 15:45     ` Andreas Enge
2024-10-21 15:53       ` Divya Ranjan
2024-10-22  8:43         ` Efraim Flashner
2024-10-22  9:29           ` Divya
2024-10-21 15:07 ` Saku Laesvuori [this message]
2024-10-21 15:39   ` Lars-Dominik Braun
2024-10-21 15:49     ` Divya Ranjan
2024-10-22 14:32       ` Lars-Dominik Braun
2024-10-22 14:50         ` Divya
2024-10-22 15:07           ` Jordan Moore
2024-10-21 15:44   ` Divya Ranjan

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=pjncwz422naeegjafzaepmoblpwtgnqm32hgml4tkqepqqswao@mws3a62ryann \
    --to=saku@laesvuori.fi \
    --cc=divya@subvertising.org \
    --cc=guix-devel@gnu.org \
    /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).