A build ask whose job built an artifact asks the new step build_go_imports once: `go list -deps` of each Go bundle's program, no tests, the forge's packages outside the module's own directory (a sibling package of the same repository counts), sorted and each once. The answer carries them as BuildAnswer.Imports. The step is also a tool, to read them by hand. Claude-Session: https://claude.ai/code/session_01NcbgfJ9Gum47zkFKWRaovL
15 lines
483 B
Go
15 lines
483 B
Go
package buildcpu
|
|
|
|
import (
|
|
"testing"
|
|
|
|
"git.novox.be/novox/mesh-sdk/go/catalogue"
|
|
)
|
|
|
|
// The share's names the composer gives are the build modules' (catalogue writes them too, so it does not import this).
|
|
func TestTheShareNamesAgreeWithTheCatalogues(t *testing.T) {
|
|
if ShareSetting != catalogue.BuildCPUShareSetting || ShareWord != catalogue.BuildCPUShareWord || DefaultPercent != catalogue.BuildCPUDefaultPercent {
|
|
t.Fatal("buildcpu's share names differ from catalogue's")
|
|
}
|
|
}
|