| commit | 2666ed6287c1b96924b52a1c8402191b853df86d | [log] [tgz] |
|---|---|---|
| author | Heschi Kreinick <heschi@google.com> | Wed Oct 05 16:11:31 2022 -0400 |
| committer | Heschi Kreinick <heschi@google.com> | Wed Oct 05 20:17:17 2022 +0000 |
| tree | 0597ef29b70d44723e1fc50021771f5c002a64c7 | |
| parent | 2adab6b8c60e0c59d67a6c737a5f1d0623751e95 [diff] |
go.mod: ignore cyclic dependency for tagging tools and mod have a cyclic dependency, which needs to be broken during the upgrading/tagging process. This direction is due to the use of txtar in the tests for the zip package, which is much less important than the other direction. For golang/go#48523. Change-Id: Id5006280b0bc6b39f191b0281d542d251d80fff5 Reviewed-on: https://go-review.googlesource.com/c/mod/+/439335 Reviewed-by: Bryan Mills <bcmills@google.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gopher Robot <gobot@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.