From: Timothy Sample <samplet@ngyro.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 36653-done@debbugs.gnu.org, Robert Vollmert <rob@vllmrt.net>
Subject: bug#36653: [PATCH v2] guix import stackage: default to a LTS release compatible with GHC 8.4
Date: Tue, 03 Nov 2020 15:55:00 -0500 [thread overview]
Message-ID: <87tuu6not7.fsf@ngyro.com> (raw)
In-Reply-To: <87lfvrew5m.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sat, 17 Aug 2019 15:52:53 +0200")
Hello,
Over a year later, and I finally went ahead and pushed this! See commit
f0bb2662bb05625042094e124521197c5f43505e.
Ludovic Courtès <ludo@gnu.org> writes:
> Robert Vollmert <rob@vllmrt.net> skribis:
>
>> +;;; Latest LTS version compatible with bundled ghc version.
>> +(define %default-lts-version "12.26")
>
> What about storing this elsewhere? Perhaps in the ‘properties’ field of
> the ‘ghc’ package? That should make it easier to keep these numbers in
> sync.
That’s true, but we already have this problem with the Hackage importer.
It has a version-specific list of packages included with GHC. It’s true
that two wrongs don’t make a right, but having this patch in place –
even with shortcomings – will prevent real problems. Besides, we can
always fix it later.
> Besides, it’s usually clearer to separate unrelated cleanups, but it’s
> no big deal in this case.
Agreed. (The typos were fixed in the interim, but I let the “https”
change hitch a ride along with the LTS version stuff.)
Anyway, this will pave the way for a lint check and then we can finally
put an end to the Haskell package roll-backs. :)
-- Tim
prev parent reply other threads:[~2020-11-03 20:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 19:38 [bug#36653] [PATCH] guix import stackage: default to a LTS release compatible with GHC 8.4 Robert Vollmert
2019-07-16 13:41 ` [bug#36653] [PATCH v2] " Robert Vollmert
2019-08-17 13:52 ` Ludovic Courtès
2020-11-03 20:55 ` Timothy Sample [this message]
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=87tuu6not7.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=36653-done@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=rob@vllmrt.net \
/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).