all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: John Kehayias <john.kehayias@protonmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
	Xinglu Chen <public@yoctocell.xyz>
Subject: Re: Create branch for Haskell build changes and updates?
Date: Fri, 09 Jul 2021 18:44:34 +0200	[thread overview]
Message-ID: <87zguvqvwt.fsf@elephly.net> (raw)
In-Reply-To: <B5dVsYiz6jkd6_i-ZcpQYr06ZT40h41DATUUE3VjsTMRac58ozGSfOWcbYhCrbWa3cSiDLQWTTvri0ioj-2SwXn_tTurRcXMCYIByWkAn8k=@protonmail.com>


Hi John,

> I'm pretty confident my build system patch 
> https://issues.guix.gnu.org/49199 works well as far as I've 
> tested it. However, for things like GHC, that would require a 
> lot of compile time and package updates everywhere I think, and 
> I personally don't have the resources/time to do that.

I could branch wip-haskell off of core-updates and apply that 
patch, then add a build farm job for wip-haskell.

Would that help?

-- 
Ricardo


  reply	other threads:[~2021-07-09 16:45 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-05 17:24 Create branch for Haskell build changes and updates? John Kehayias
2021-07-07  5:47 ` Xinglu Chen
2021-07-07 14:47   ` John Kehayias
2021-07-07 15:02     ` John Soo
2021-07-08 17:45     ` Xinglu Chen
2021-07-09 14:06       ` Ricardo Wurmus
2021-07-09 15:21         ` John Kehayias
2021-07-09 16:44           ` Ricardo Wurmus [this message]
2021-07-09 18:45             ` John Kehayias
2021-07-10 15:39           ` Xinglu Chen
2021-07-20 11:58             ` Philip Munksgaard
2021-07-20 16:49               ` Ricardo Wurmus
2021-07-20 19:41                 ` Philip Munksgaard
2021-07-21 21:10                 ` Ricardo Wurmus
2021-07-27 21:24                   ` John Kehayias
2021-07-27 21:34                     ` Ricardo Wurmus
2021-07-20 22:24   ` Ricardo Wurmus
2021-07-24 13:40     ` Xinglu Chen
2021-07-24 15:00       ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zguvqvwt.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=john.kehayias@protonmail.com \
    --cc=public@yoctocell.xyz \
    /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.