From: Hilton Chain via Guix-patches via <guix-patches@gnu.org>
To: 66723@debbugs.gnu.org
Cc: "Nguyễn Gia Phong" <mcsinyx@disroot.org>,
"Ludovic Courtès" <ludo@gnu.org>,
"Ekaitz Zarraga" <ekaitz@elenq.tech>
Subject: [bug#66723] [PATCH 0/3] gnu: zig-0.10: Inherit from zig-0.9.
Date: Thu, 23 Nov 2023 23:23:05 +0800 [thread overview]
Message-ID: <87cyw0trxi.wl-hako@ultrarare.space> (raw)
In-Reply-To: <87wmuakmv8.fsf@gnu.org>
Hi,
On Sun, 19 Nov 2023 19:35:13 +0800, Nguyễn Gia Phong wrote:
>
> Should we keep Zig 0.9? All currently packaged Zig programs requires it
> anymore AFAICT, and the language is immature enough I'd argue we should only
> keep older versions when necessary.
>
> Your patchset adding LLVM 16 has been applied BTW, I can't wait for Zig 0.11!
I didn't realise that Zig 0.11 includes a binary file when sending the cover
letter. So I haven't bootstrapped it yet, sorry that I didn't mention this
earlier...
Though Zig 0.11 is not bootstrapped, here's a patch to use it at the moment:
https://paste.sr.ht/~hako/c6fb3a872c1e91a09500bf1288e128215ca80d12
I have no experience in both bootstrapping and Zig, so I don't know exactly what
to do further.
(Cc-ed Ekaitz since they are more familiar with the topic)
For Zig I think the first step is to create a path from the last commit that has
a stage1:
4e2a960b523070c7f8fddf0ea9b6e2a94e31dafe (std.fs: fix openDirAbsolute)
to the addition of the binary file:
20d86d9c63476b6312b87dc5b0e4aa4822eb7717 (add zig1.wasm.zst)
But for now I'm not sure how.
On Wed, 22 Nov 2023 20:12:43 +0800, Ludovic Courtès wrote:
>
> Hi Hilton,
>
> Hilton Chain <hako@ultrarare.space> skribis:
>
> > This series applies gexp to package arguments of zig@0.9 and zig@0.10, and
> > makes the latter inherit from the former.
> >
> > I have already packaged zig@0.11, which depends on LLVM 16
> > (https://issues.guix.gnu.org/66701), will send the patch soon.
> >
> > Hilton Chain (3):
> > gnu: zig-0.10: Use gexp.
> > gnu: zig-0.9: Use gexp.
> > gnu: zig-0.10: Inherit from zig-0.9.
>
> It’s been a while, and I think this patch series can go in.
>
> As Nguyễn Gia Phong, we should question whether to keep zig 0.9, but that can
> come later.
Thank you! I'll push the series this weenkend.
next prev parent reply other threads:[~2023-11-23 15:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-24 8:23 [bug#66723] [PATCH 0/3] gnu: zig-0.10: Inherit from zig-0.9 Hilton Chain via Guix-patches via
2023-10-24 8:34 ` [bug#66723] [PATCH 1/3] gnu: zig-0.10: Use gexp Hilton Chain via Guix-patches via
2023-10-24 8:34 ` [bug#66723] [PATCH 2/3] gnu: zig-0.9: " Hilton Chain via Guix-patches via
2023-10-24 8:34 ` [bug#66723] [PATCH 3/3] gnu: zig-0.10: Inherit from zig-0.9 Hilton Chain via Guix-patches via
2023-11-19 11:35 ` [bug#66723] [PATCH 0/3] " guix-patches--- via
2023-11-23 15:23 ` Hilton Chain via Guix-patches via [this message]
2023-11-23 16:23 ` Ekaitz Zarraga
2023-11-25 14:10 ` bug#66723: " Hilton Chain via Guix-patches via
2023-11-22 12:12 ` [bug#66723] " Ludovic Courtès
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=87cyw0trxi.wl-hako@ultrarare.space \
--to=guix-patches@gnu.org \
--cc=66723@debbugs.gnu.org \
--cc=ekaitz@elenq.tech \
--cc=hako@ultrarare.space \
--cc=ludo@gnu.org \
--cc=mcsinyx@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 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.