From 9c4d668c926e2d9eae6ef87cd9b391d8185605f9 Mon Sep 17 00:00:00 2001 From: Gabriel Schneider Date: Mon, 21 Sep 2026 17:15:19 -0300 Subject: Package 9harness: the published tarball was missing it MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit build.zig @imports each program's build fragment unconditionally, so a program absent from .paths builds fine from a checkout and fails for every consumer with zig-pkg/cloud9-.../9harness/build.zig: unable to load 'build.zig': FileNotFound 9ns and 9proc were listed; 9harness was not, from the change that added it. A pardes build against cloud9 main found it — the first consumer to try. Nothing in the suites covers "the package a dependent fetches actually builds", which is why it went unnoticed. --- build.zig.zon | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/build.zig.zon b/build.zig.zon index a7a4e3b..d042fe3 100644 --- a/build.zig.zon +++ b/build.zig.zon @@ -3,5 +3,15 @@ .fingerprint = 0xc8b2d5eaa3adfca, .version = "0.1.0", .minimum_zig_version = "0.16.0", - .paths = .{ "build.zig", "build.zig.zon", "src", "web", "test", "docs", "README.md", "9ns", "9proc" }, + // Every directory build.zig reaches into must be here, or the + // published package cannot build: build.zig @imports each program's + // build fragment unconditionally, so a program missing from this + // list is a FileNotFound for every consumer, while building fine + // from a checkout. 9harness was exactly that until a pardes build + // caught it. + .paths = .{ + "build.zig", "build.zig.zon", "src", "web", + "test", "docs", "README.md", + "9ns", "9proc", "9harness", + }, } -- cgit v1.3