build: commands sharing a basename silently clobber each other #65

New issue

Open

opened 2026-05-22 00:17:13 +02:00 by heiko · 1 comment

heiko commented

2026-05-22 00:17:13 +02:00

Owner

Two build.commands entries that share a basename (e.g. cmd/foo and legacy/foo) both produce a binary called foo. They clobber each other in the output directory and — for explicit artifacts.packages configs — the binaries matching is basename-only, so it is impossible to route them to separate packages.

Discovered while fixing the packages[*].binaries full-path acceptance (PR upcoming). That fix normalises binary identifiers to basenames at load time, which makes the limitation visible as a correct double-claim validation error rather than a silent runtime failure.

The fix would require preserving the full Go package path through build.Result and updating all downstream consumers (binary matching, packaging, source package generation) to use a path-qualified identifier. This is a non-trivial refactor; tracking here for future work.

Two `build.commands` entries that share a basename (e.g. `cmd/foo` and `legacy/foo`) both produce a binary called `foo`. They clobber each other in the output directory and — for explicit `artifacts.packages` configs — the `binaries` matching is basename-only, so it is impossible to route them to separate packages. Discovered while fixing the `packages[*].binaries` full-path acceptance (PR upcoming). That fix normalises binary identifiers to basenames at load time, which makes the limitation visible as a correct double-claim validation error rather than a silent runtime failure. The fix would require preserving the full Go package path through `build.Result` and updating all downstream consumers (binary matching, packaging, source package generation) to use a path-qualified identifier. This is a non-trivial refactor; tracking here for future work.

heiko added the

Kind/Bug

label

2026-05-22 00:17:13 +02:00

heiko referenced this issue

2026-05-22 00:27:04 +02:00

config: packages[*].binaries should accept full Go package paths #67

heiko commented

2026-05-22 11:38:38 +02:00

Author

Owner

AI attribution comment added per repository instruction for this open issue.\n\n(co)authored by ai:gpt-5-codex