On Wed Nov 11, 2026 at 8:09 AM GMT, Edmund Lodewijks wrote:
I thought that the bootstrap was the real blocker, but it turns out that the vendored code was. That's were my effort should go next then.

By coincidence I was discussing Zig packaging (which I have nothing to do with) on Lobsters with one of the Zig maintainers. They wrote[1]:

As for vendored dependencies, this is a complete list:

 * C language include files from Clang
 * libc include files and implementation files for various targets
 * libc++, libc++abi, libtsan, and libunwind from Clang

The whole (short) thread may be of interest. He went on to write

Let me ask this question though: what is the purpose of packaging Zig into Debian? In my opinion, upstream developers prefer to obtain Zig directly from upstream. I think the purpose of packaging Zig into Debian is not for Zig users but so that Zig can be used as a development package to build other Debian packages. In this case, you don't need any cross-compilation support or any of these vendored dependencies. They can be completely omitted from the package. This hamstrings Zig as a compiler tool, so it would be appreciated if it were made clear to Zig users that this package is not for them. But I think that is a path worth exploring for Debian, if the goal is to build other packages.

[1] https://lobste.rs/c/kmr7ar

--
⢀⣴⠾⠻⢶⣦⠀
⣾⠁⢠⠒⠀⣿⡁ Jonathan Dowland
⢿⡄⠘⠷⠚⠋⠀ https://jmtd.net
⠈⠳⣄⠀⠀⠀⠀

Reply via email to