From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "Antero Mejr" <antero@mailbox.org>
Cc: "55606@debbugs.gnu.org" <55606@debbugs.gnu.org>,
Tobias Geerinckx-Rice <me@tobias.gr>,
Maxime Devos <maximedevos@telenet.be>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Subject: [bug#55606] [PATCH 2/2] gnu: Add hare.
Date: Sun, 24 Jul 2022 17:10:09 +0100 [thread overview]
Message-ID: <CLO0MXRILE1Z.4XAE4TMFRA4L@guix-aspire> (raw)
In-Reply-To: <87bkuffquv.fsf@mailbox.org>
On Sun Jun 26, 2022 at 3:07 PM BST, Antero Mejr wrote:
> If we moved qbe/harec to inputs, we could patch os::tryenv in
> schedule.ha to resolve to the guix path. That way the user gets a
> working toolchain by default, but they could still swap in different
> versions of qbe/harec using the QBE/HAREC environment variables.
Yes, that's what I meant. (Sorry for the late reply :))
-- (
next prev parent reply other threads:[~2022-07-24 16:11 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-24 1:21 [bug#55605] [PATCH 1/2] gnu: Add qbe Antero Mejr via Guix-patches via
2022-05-24 1:21 ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-05-24 17:01 ` Maxime Devos
2022-05-24 17:07 ` Maxime Devos
2022-05-24 17:09 ` Maxime Devos
2022-05-24 17:10 ` Tobias Geerinckx-Rice via Guix-patches via
2022-05-29 0:54 ` [bug#55606] [PATCH] " Antero Mejr via Guix-patches via
2022-06-03 17:54 ` [bug#55606] Antero Mejr via Guix-patches via
2022-06-25 16:54 ` [bug#55606] [PATCH 2/2] gnu: Add hare Liliana Marie Prikler
2022-06-25 17:53 ` ( via Guix-patches via
2022-06-26 4:56 ` Antero Mejr via Guix-patches via
2022-06-25 17:59 ` ( via Guix-patches via
2022-06-26 4:40 ` Antero Mejr via Guix-patches via
2022-06-26 7:30 ` Maxime Devos
2022-06-26 7:34 ` Maxime Devos
2022-06-26 10:58 ` ( via Guix-patches via
2022-06-26 14:07 ` Antero Mejr via Guix-patches via
2022-06-26 14:27 ` Maxime Devos
2022-06-26 14:39 ` Antero Mejr via Guix-patches via
2022-07-24 16:10 ` ( via Guix-patches via [this message]
2022-06-25 21:32 ` Antero Mejr via Guix-patches via
2022-06-26 4:39 ` [bug#55606] [PATCH 1/2] gnu: Add harec Antero Mejr via Guix-patches via
2022-06-26 4:39 ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-06-26 7:18 ` Liliana Marie Prikler
2022-06-26 11:05 ` ( via Guix-patches via
2022-06-26 14:00 ` Antero Mejr via Guix-patches via
2022-06-26 6:50 ` [bug#55606] [PATCH 1/2] gnu: Add harec Liliana Marie Prikler
2022-06-26 13:59 ` Antero Mejr via Guix-patches via
2022-06-26 13:59 ` [bug#55606] [PATCH 2/2] gnu: Add hare Antero Mejr via Guix-patches via
2022-06-26 14:20 ` Maxime Devos
2022-06-26 14:30 ` Antero Mejr via Guix-patches via
2022-06-26 14:39 ` Maxime Devos
2022-06-26 14:22 ` Maxime Devos
2022-06-26 14:33 ` Antero Mejr via Guix-patches via
2022-06-26 14:44 ` Maxime Devos
2022-06-26 14:53 ` Maxime Devos
2022-05-24 16:56 ` [bug#55605] [PATCH 1/2] gnu: Add qbe Maxime Devos
2022-05-24 21:06 ` Maxime Devos
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=CLO0MXRILE1Z.4XAE4TMFRA4L@guix-aspire \
--to=guix-patches@gnu.org \
--cc=55606@debbugs.gnu.org \
--cc=antero@mailbox.org \
--cc=liliana.prikler@gmail.com \
--cc=maximedevos@telenet.be \
--cc=me@tobias.gr \
--cc=paren@disroot.org \
/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).