unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Divya <divya@subvertising.org>
To: Lars-Dominik Braun <lars@6xq.net>
Cc: Saku Laesvuori <saku@laesvuori.fi>, guix-devel@gnu.org
Subject: Re: Haskell & Rust Team on recent stable releases of compilers
Date: Tue, 22 Oct 2024 14:50:07 +0000	[thread overview]
Message-ID: <5B275ADB-6569-4401-B3CF-D3C6B1119F3B@subvertising.org> (raw)
In-Reply-To: <Zxe3aAdCv-lvb0rm@noor.fritz.box>

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

On 22 October 2024 14:32:08 GMT, Lars-Dominik Braun <lars@6xq.net> wrote:
>Hi,
>
>> Is there a specific reason why we’re following the Stackage releases? Stackage is one step slower in getting the updates. The current Stackage Nightly is 9.8.2, while Hackage has 9.10.1. Is this due to some stability issues with Hackage?
>
>Stackage’s package collection is coherent and so we don’t have to
>manually deal with and resolve dependency conflicts. (Currently the
>Hackage/Stackage importer cannot pick the correct package version for
>dependencies when importing or updating a package.)
>
>Lars
>

Understood. Makes sense.

[-- Attachment #2: Type: text/html, Size: 1146 bytes --]

  reply	other threads:[~2024-10-22 14:51 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
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 [this message]
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=5B275ADB-6569-4401-B3CF-D3C6B1119F3B@subvertising.org \
    --to=divya@subvertising.org \
    --cc=guix-devel@gnu.org \
    --cc=lars@6xq.net \
    --cc=saku@laesvuori.fi \
    /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).