Use selected module for dependency downloads
This commit is contained in:
@@ -33,7 +33,9 @@ coexist. Disk-backed diagnostics could reduce large failure peaks, but add file
|
||||
lifecycle and cleanup work and remain a follow-up option.
|
||||
|
||||
Dependency preparation uses a separate command environment so proxy, private
|
||||
module, checksum, and cache settings remain available. Its completed capture
|
||||
module, checksum, cache, and other effective settings remain available. Its
|
||||
`go mod download -modfile=` command overrides an alternate module file selected
|
||||
through `GOFLAGS`, preserving ordinary module discovery. Its completed capture
|
||||
uses the same ownership transfer when formatting a failure.
|
||||
|
||||
## Configuration discovery
|
||||
|
||||
@@ -208,7 +208,8 @@ composition with ordinary build identity and ambient flags.
|
||||
|
||||
## Stage 4: Override alternate module-file selection during downloads
|
||||
|
||||
**Status:** pending.
|
||||
**Status:** complete. `go test ./internal/gotool` passes offline. Actual module
|
||||
graph selection evidence remains deferred to Stage 5.
|
||||
|
||||
**Files:** `internal/gotool/gotool.go`, `internal/gotool/gotool_test.go`,
|
||||
`preparation.go` GoDoc, and `docs/internal/gotool.md`.
|
||||
|
||||
Reference in New Issue
Block a user