unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
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 16:57:43 +0200	[thread overview]
Message-ID: <ZxZr5x1RnRDkMtx0@jurong> (raw)
In-Reply-To: <792C5AC3-5268-4073-8EF4-D88C1EDCE072@subvertising.org>

Hello Divya,

I would like to only reply to your last point:

Am Mon, Oct 21, 2024 at 02:50:43PM +0000 schrieb Divya:
> Regarding copyright assignment, I've already started the paperwork by emailing
> the form to assign@gnu.org. I did it through Emacs, but I believe I don't need
> to do it again? Some guidance for that would also be helpful.

No need to assign copyright for work on Guix, we keep the individual
contributors.

But I may as well comment on the other ones and have myself corrected by more
knowlegeable people from the corresponding teams.

> 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?
> 
> 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.

There should not be a difference with packages for other languages.
As far as I know, however, ghc is annoying to bootstrap, and we need at
least the latest x.y.z version to continue to x.(y+2).

> The same is true for rustc, the latest stable release is not updated. I'd like
> to help with that, if possible.

For rust, there is a special branch rust-team, where the work is coordinated.

Andreas



  reply	other threads:[~2024-10-21 14:58 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 [this message]
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
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=ZxZr5x1RnRDkMtx0@jurong \
    --to=andreas@enge.fr \
    --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).