From: Timothy Sample <samplet@ngyro.com>
To: John Soo <jsoo1@asu.edu>, Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: merge wip-haskell?
Date: Fri, 07 Aug 2020 13:46:56 -0400 [thread overview]
Message-ID: <87h7tes60f.fsf@ngyro.com> (raw)
In-Reply-To: <F3E41D33-B1B9-4DDC-80F5-F473D703F3CA@asu.edu> (John Soo's message of "Thu, 6 Aug 2020 06:45:39 -0700")
Hi John and Ricardo,
John Soo <jsoo1@asu.edu> writes:
> I believe there was also some work being done to de-duplicate flags
> sent to gcc sent by ghc (this was the only thing keeping stack from
> building).
> I hope that can make it in, too!
I agree, and sorry to you John for the delay. I’m not using much
Haskell these days, so I’m having trouble keeping Haskell stuff on my
radar. The last patch I sent to <https://issues.guix.gnu.org/39309> is
about as good as I can come up with, so I will apply it to the branch
before the merge.
Ricardo, I will try and do this tonight or tomorrow, and will look over
your changes then as well.
> If there is any way we can bump the default ghc to 8.8.x, that would
> be excellent, too. I think something like that makes sense on staging
> though.
I would love for this to happen, but I think it would needlessly delay
Ricardo’s changes. Fortunately, one can build all of our Haskell
packages overnight on a modest computer, so it’s no big deal to merge
the branch now and then merge the GHC 8.8.x updates whenever they’re
ready.
Also, it looks like “wip-haskell-updates” is no longer being built by
the CI infrastructure. Since the branch triggers a rebuild of all the
Haskell packages, it should be built before merging, right?
-- Tim
next prev parent reply other threads:[~2020-08-07 17:47 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-06 8:13 merge wip-haskell? Ricardo Wurmus
2020-08-06 13:45 ` John Soo
2020-08-07 17:46 ` Timothy Sample [this message]
2020-08-07 19:53 ` Ricardo Wurmus
2020-08-09 4:29 ` Timothy Sample
2020-08-12 12:21 ` Ricardo Wurmus
2020-08-13 15:37 ` Ricardo Wurmus
2020-08-15 8:19 ` Ricardo Wurmus
2020-08-17 15:22 ` Timothy Sample
2020-08-24 15:38 ` Ludovic Courtès
2020-08-07 15:03 ` Jakub Kądziołka
2020-08-07 15:12 ` John Soo
2020-08-07 15:46 ` Jakub Kądziołka
2020-08-07 15:59 ` Ricardo Wurmus
2020-08-07 16:08 ` John Soo
2020-08-24 15:44 ` Ludovic Courtès
2020-08-24 17:54 ` Ricardo Wurmus
2020-08-28 13:53 ` Ludovic Courtès
2020-08-28 14:05 ` John Soo
2020-08-28 17:29 ` Timothy Sample
2020-08-29 15:34 ` Timothy Sample
2020-08-29 15:54 ` John Soo
2020-08-07 16:27 ` Ricardo Wurmus
2020-08-07 16:55 ` Jakub Kądziołka
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=87h7tes60f.fsf@ngyro.com \
--to=samplet@ngyro.com \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
--cc=rekado@elephly.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).