From: John Kehayias <john.kehayias@protonmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: Xinglu Chen <public@yoctocell.xyz>,
"guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Create branch for Haskell build changes and updates?
Date: Fri, 09 Jul 2021 15:21:12 +0000 [thread overview]
Message-ID: <B5dVsYiz6jkd6_i-ZcpQYr06ZT40h41DATUUE3VjsTMRac58ozGSfOWcbYhCrbWa3cSiDLQWTTvri0ioj-2SwXn_tTurRcXMCYIByWkAn8k=@protonmail.com> (raw)
In-Reply-To: <8735snshsf.fsf@elephly.net>
On Friday, July 9th, 2021 at 10:06 AM, Ricardo Wurmus wrote:
> Sorry, not this time :)
>
> I suggest just starting a new branch. It doesn’t really need to
>
> be hosted in the main repo at this point, but if you have some
>
> initial patches that you’d like me to push to wip-haskell feel
>
> free to send them.
>
Hi Ricardo,
Yes, we could have a repo anywhere, but what (at least) I was getting at was having some CI support to build Haskell packages to find any breakage. Even without being on the main repo could we do that? Changes I've made locally and packages I've tried to add (which might need version bumps of others) lead to a ton of compile time.
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.
We could at least get a mirror from core-updates(?) to base off of and add some patches for individual testing. Maybe anyone who wants to lead a GHC update can weigh in on resources needed to make it doable (as that I would imagine needs the most time to do)?
John
next prev parent reply other threads:[~2021-07-09 15:22 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 [this message]
2021-07-09 16:44 ` Ricardo Wurmus
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='B5dVsYiz6jkd6_i-ZcpQYr06ZT40h41DATUUE3VjsTMRac58ozGSfOWcbYhCrbWa3cSiDLQWTTvri0ioj-2SwXn_tTurRcXMCYIByWkAn8k=@protonmail.com' \
--to=john.kehayias@protonmail.com \
--cc=guix-devel@gnu.org \
--cc=public@yoctocell.xyz \
--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 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.