nick black left as an exercise for the reader: > > The bootstrap is circular and has to be kicked off with a binary blob that > > can't be recreated until one has finished the bootstrap, which is > > certainly not ideal, but is also not that atypical for compiler > > bootstrapping problems. I don't see how this is a violation of the DFSG or > > of the requirement that main be self-contained. It's obnoxious from a > > process standpoint (like a lot of compiler bootstrapping), and we may not > > want things to work this way, but I don't think that makes it non-free? > > what you say here makes perfect sense; i'll look at what gcc and > friends are doing, thanks!
i had thought that there was a Policy directive prohibiting generated files in source packages, but rereading 4.7.0.2, i don't see such a thing. we do see in debmake-doc [0]: "Extraneous auto-generated contents in the upstream source. Debian package should rebuild them under the latest system." so yeah, this seems pretty reasonable, and i'm surprised i didn't think of it. i do think that it would be best to rebuild the binary wasm file after having bootstrapped up zig, though that wouldn't be strictly necessary to bootstrap. that way we're shipping something we built, and verify the toolchain can build it. thanks as always, russ! [0] https://www.debian.org/doc/manuals/debmake-doc/ch07.en.html -- nick black -=- https://nick-black.com to make an apple pie from scratch, you need first invent a universe.
signature.asc
Description: PGP signature
