diff options
Diffstat (limited to '_content/doc/modules/managing-dependencies.md')
| -rw-r--r-- | _content/doc/modules/managing-dependencies.md | 7 |
1 files changed, 5 insertions, 2 deletions
diff --git a/_content/doc/modules/managing-dependencies.md b/_content/doc/modules/managing-dependencies.md index 957f31a1..06c129f0 100644 --- a/_content/doc/modules/managing-dependencies.md +++ b/_content/doc/modules/managing-dependencies.md @@ -534,9 +534,12 @@ pruning, when you depend on a module that itself has a tool dependency, requirements that exist just to satisfy that tool dependency do not usually become requirements of your module. -The `tool` [meta-pattern](/cmd/go#hdr-Package_lists_and_patterns) provides a way to perform operations on all tools simultaneously. For example you can upgrade all tools with `go get -u tool`, or install them all to $GOBIN with `go install tool`. +The `tool` [meta-pattern](/cmd/go#hdr-Package_lists_and_patterns) provides a way to perform operations on all +tools simultaneously. For example you can upgrade all tools with `go get tool`, +which is equivalent to `go get tool@upgrade`, or install them all to $GOBIN +with `go install tool`. -In Go versions before 1.24, you can acheive something similar to a `tool` +In Go versions before 1.24, you can achieve something similar to a `tool` directive by adding a blank import to a go file within the module that is excluded from the build using [build constraints](/pkg/go/build/#hdr-Build_Constraints). If you do this, you can then |