Extracted from #14265.
This would have the following benefits:
Perhaps there could be some other linty checks that it would do by default, which would make people feel happy feelings when publishing a package.
However, there's kind of an odd downside here - this feature would not be necessary. By intention, any tarball generated by any service - even from any arbitrary commit - should work fine. The existence of this feature might mislead people into thinking that publishing a zig package is more complicated than it really is.
Extracted from #14265.
This would have the following benefits:
build.zig.zonfirst in the tar (less important if make build.zig.zon contain all urls, including mirrors, and hashes of entire dependency tree #14309 is implemented)Perhaps there could be some other linty checks that it would do by default, which would make people feel happy feelings when publishing a package.
However, there's kind of an odd downside here - this feature would not be necessary. By intention, any tarball generated by any service - even from any arbitrary commit - should work fine. The existence of this feature might mislead people into thinking that publishing a zig package is more complicated than it really is.