-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 The bootstrap is the first obstacle. Fortunately, Guix did the hard work it just needs to be ported to Debian. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1150314 tracks my attempt at porting it to Debian.
The second obstacle is the unvendoring. After I had a working version of the bootstrap, I consulted with multiple DDs. Arthur ([email protected]) found the issues with vendoring right away. Since then, Jesse ([email protected]) has been working on unvendoring and on packaging Ghostty in parallel. https://salsa.debian.org/jmrx/zig/-/commits/debian/latest?pow_referer=&ref_type=HEADS has his progress. From a quick look, they match what was reported (libc, libc++, sanitizers, etc). I was talking to Edmund off the mailing list, but to make it public: thanks for finding the hops from 0.16 to 0.17 that is useful work. Regardless of how it happens, I am looking forward to the day packages written in Zig can be distributed by Debian. Ghostty will be the poster child but more will come. -----BEGIN PGP SIGNATURE----- iQIzBAEBCgAdFiEEVvJVXB5OVWvTtRKOUzWXp/WttbYFAmr0f18ACgkQUzWXp/Wt tbZX1g//X79l25TdvUMJwtXN7L2xOqsfo3uz6ZFCF735JTi/18YpC4EhSqqe93UQ /c7tCibqty3RcolXiOPadq+lTO6eXf9CrxskwrPpagTayiCg9EfrYfjxa6koGEXE 6WsekCvg4tASN2MwPI3W4BmnkfKCofgLh0MT8oneLLE3lPh+Txoa9ibHcZC/zbYn 0DMQwPGfQ7E/U4bG4gL2JQU4ZM7T1HtUM+UAduUAFvIoc9te8y03VA2jAhDfNvtg zuElPgaIlG0vQz4He+wPWMBD47rI3Qc8bbOAfzxpxlEKct2rDZmQhUUMmwR9YpNP 2ITXq2jk1bZc82cfBmaZwtdvo6QHodE5zyoz6aGaBthHrdT432uLGeYUSaZIQUFV NTd8IPlBvngZa/Ztf4KzSnrSNPdzS0OukxIWhWnMbabrnLk3e2L6RFxqF79UiY+o vYQHVKGfCM8rx2pfuO0Hn2u+BJKNFWgRHghySHVy8Z+daXd34fOZoZV2/jwDI+cR GspwFYJEbq59x1VH6c8MAX3b/yaqMxfaD4SfNllHaka5YTFEffYWM4ZrKZmPmpHx bPZ/m0N6RBzy7tVEoS4k+EqbeaXDNQ12BbMMEazC3EWDqPoVUh/ION0WsjUwD7M8 OZw+93H4afOmaAz66E9fTWGVB4Mu/QppWXcyToeVf5anNkdTHuM= =T5js -----END PGP SIGNATURE----- On Wed, Nov 11, 2026 at 6:18 AM Jonathan Dowland <[email protected]> wrote: > > 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 > ⠈⠳⣄⠀⠀⠀⠀ >

