| commit | bc151c4e8ccc31931553c47d43e41c0efc246096 | [log] [tgz] |
|---|---|---|
| author | Mike Seplowitz <mseplowitz@bloomberg.net> | Mon Jul 29 10:02:17 2024 -0400 |
| committer | Gopher Robot <gobot@golang.org> | Tue Jul 30 14:22:55 2024 +0000 |
| tree | 4d922f77215c49797dece39f425adb9d2e07460b | |
| parent | d1f873e3c1b2cf7231a30697aea158ae6cfdbb5f [diff] |
README: fix link to x/tools Change-Id: I4803bfe7da3b21fdfe503b9804015f0a5104a52e Reviewed-on: https://go-review.googlesource.com/c/mod/+/601441 Reviewed-by: Ian Lance Taylor <iant@google.com> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Auto-Submit: Ian Lance Taylor <iant@google.com> Reviewed-by: Michael Knyszek <mknyszek@google.com>
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.