@@ -482,18 +482,22 @@ To eliminate ambiguity about which module versions are used in the build, the
482
482
arguments must satisfy the following constraints:
483
483
484
484
- Arguments must be package paths or package patterns (with "..." wildcards).
485
- They must not be standard packages (like fmt), meta-patterns (std, cmd,
486
- all), or relative or absolute file paths.
485
+ They must not be standard packages (like fmt), meta-patterns (std, cmd,
486
+ all), or relative or absolute file paths.
487
+
487
488
- All arguments must have the same version suffix. Different queries are not
488
- allowed, even if they refer to the same version.
489
+ allowed, even if they refer to the same version.
490
+
489
491
- All arguments must refer to packages in the same module at the same version.
492
+
490
493
- No module is considered the "main" module. If the module containing
491
- packages named on the command line has a go.mod file, it must not contain
492
- directives (replace and exclude) that would cause it to be interpreted
493
- differently than if it were the main module. The module must not require
494
- a higher version of itself.
494
+ packages named on the command line has a go.mod file, it must not contain
495
+ directives (replace and exclude) that would cause it to be interpreted
496
+ differently than if it were the main module. The module must not require
497
+ a higher version of itself.
498
+
495
499
- Package path arguments must refer to main packages. Pattern arguments
496
- will only match main packages.
500
+ will only match main packages.
497
501
498
502
If the arguments don't have version suffixes, "go install" may run in
499
503
module-aware mode or GOPATH mode, depending on the GO111MODULE environment
0 commit comments