| commit | 2adab6b8c60e0c59d67a6c737a5f1d0623751e95 | [log] [tgz] |
|---|---|---|
| author | Bryan C. Mills <bcmills@google.com> | Wed Sep 21 14:21:05 2022 -0400 |
| committer | Gopher Robot <gobot@golang.org> | Thu Sep 22 19:54:21 2022 +0000 |
| tree | 3e4c42ebcfdce1c1b3ae6948a31e2093b6f384ff | |
| parent | 02c991387e35f9e4c0a9b7ce137717055f8d716d [diff] |
zip: expand logging and use t.TempDir and t.Cleanup in test helpers Fixes golang/go#55250 (for now). Change-Id: I7286c459937e666d3e88fe56a9af1a2ff22f0186 Reviewed-on: https://go-review.googlesource.com/c/mod/+/432475 Auto-Submit: Bryan Mills <bcmills@google.com> Run-TryBot: Bryan Mills <bcmills@google.com> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Michael Matloob <matloob@golang.org>
This repository holds packages for writing tools that work directly with Go module mechanics. That is, it is for direct manipulation of Go modules themselves.
It is NOT about supporting general development tools that need to do things like load packages in module mode. That use case, where modules are incidental rather than the focus, should remain in x/tools, specifically x/tools/go/packages.
The specific case of loading packages should still be done by invoking the go command, which remains the single point of truth for package loading algorithms.