From: "Jordan Moore" <lockbox@struct.foo>
To: Divya <divya@subvertising.org>, "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 11:07:43 -0400 [thread overview]
Message-ID: <8a8e9aa0-c013-4f15-bd3a-daec3251b6e2@app.fastmail.com> (raw)
In-Reply-To: <5B275ADB-6569-4401-B3CF-D3C6B1119F3B@subvertising.org>
[-- Attachment #1: Type: text/plain, Size: 1255 bytes --]
Another thing to keep in mind is that packaging for development is different than packaging for a distribution. Packaging for a distribution you only want to pull in packages from stackage that are required to build eg. xmonad or shellcheck.
However having robust importing for when those needs / maintenence on those packages arrives, and for using guix to help develop a haskell project would be a good gain. imo focusing attention on the importer(s) and the ability to import from different sources (correctly) would be the problem to tackle.
On Tue, Oct 22, 2024, at 10:50, Divya wrote:
> 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: 2239 bytes --]
next prev parent reply other threads:[~2024-10-22 15:28 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
2024-10-22 15:07 ` Jordan Moore [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8a8e9aa0-c013-4f15-bd3a-daec3251b6e2@app.fastmail.com \
--to=lockbox@struct.foo \
--cc=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 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.