From: Ricardo Wurmus <rekado@elephly.net>
To: Timothy Sample <samplet@ngyro.com>
Cc: guix-devel@gnu.org, Robert Vollmert <rob@vllmrt.net>
Subject: Re: on cabal revisions
Date: Fri, 14 Jun 2019 22:24:52 +0200 [thread overview]
Message-ID: <87a7ejrk39.fsf@elephly.net> (raw)
In-Reply-To: <87d0jgnpqz.fsf@ngyro.com>
Timothy Sample <samplet@ngyro.com> writes:
>> Is “guix refresh” even a good approach for the haskell packages? There’s
>> a lot of work being done to put consistent sets of haskell packages, e.g.
>> the whole stackage project. Does Guix mean to replicate this work, or would
>> it maybe be a good choice to follow stackage sets?
>
> We mostly do this already. There is a Stackage importer, and a little
> while ago I updated most of our Haskell packages to their LTS 12
> versions.
At the beginning we just had all the latest packages from Hackage and it
took considerable time and effort to upgrade them all to a consistent
LTS set.
This makes the review of updates to ghc-* packages a little slower for
me because these packages really ought to be upgraded together so that
they closely resemble whichever LTS version we’re following.
(This is what I’m doing for Bioconductor and CRAN packages and it would
be great if we could regularly sync our Haskell packages in the same
manner.)
--
Ricardo
next prev parent reply other threads:[~2019-06-14 20:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-11 20:56 on cabal revisions Robert Vollmert
2019-06-12 4:54 ` Timothy Sample
2019-06-13 11:46 ` Robert Vollmert
2019-06-13 14:25 ` Timothy Sample
2019-06-14 14:30 ` Robert Vollmert
2019-06-14 15:36 ` Timothy Sample
2019-06-14 20:24 ` Ricardo Wurmus [this message]
2019-06-16 8:00 ` haskell package organization (Re: on cabal revisions) Robert Vollmert
2019-06-14 20:28 ` on cabal revisions Ricardo Wurmus
2019-06-15 9:02 ` reproducibility and bootstrapping in mid 2019 (was Re: on cabal revisions) Giovanni Biscuolo
2019-06-14 20:12 ` on cabal revisions Ricardo Wurmus
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=87a7ejrk39.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=rob@vllmrt.net \
--cc=samplet@ngyro.com \
/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).