zig
Zig is a general-purpose programming language and toolchain for maintaining robust, optimal and reusable software.
Starting from version 0.11, the Zig compiler is completely self-hosted. To bootstrap the compiler, upstream provides a pre-built wasm module (stage1/zig1.wasm) and a minimal wasm2c translator implementation in the source archive (to clarify, zig1.wasm is the only pre-built file). As far as I'm aware, this falls under the 'no pre-built binaries' rule and requires an exception.
stage1/zig1.wasm
zig1.wasm
Zig is quickly evolving, and we don't expect to be able to use a previous version of the compiler to build the current one (in fact, upstream outright states that it won't be possible), therefore we'll have to re-bootstrap every (minor?) release. Consider this a blanket exception request for any future version of Zig until the stabilization of the language, and quite possibly even after that.
The current implementation of bootstrapping is available for review in the pending PR for the Zig package.
CC: @sentry
If this is what is required for building zig, then I am +1 to the bootstrap exception for this version, and any future versions that require bootstrapping.
We have this for dotnet, I have no problem with this for zig too. +1
Ping? It's been a month and the zig package in rawhide is currently FTI because of retired clang/lld compat packages. What can we do to unblock this ticket?
I'll try. @tibbs @churchyard @ignatenkobrain @james @limb @carlwgeorge please vote
We might need to add some kind of voting policy similar to the one we have for FESCo ...
For some reason I thought we had discussed this. +1 from me.
With three +1 votes after a month, I don't think it's likely that any of the other members are going to object here. So I'll go out on a limb (or whatever the correct English idiom is) and say this is approved. Feel free to continue with your plan, and if it turns out the people who didn't object in the last 6 weeks have a problem, they can blame me. ;)
I have to agree. Please just go ahead.
Login to comment on this ticket.