cybercyst/go
1
0
Fork 0
mirror of https://github.com/golang/go.git synced 2025-05-05 23:53:05 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

minor formatting

thepudds 2018-07-27 08:04:34 -04:00
parent 847a5deac8
commit 61c12ceeff
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
Modules.md

@ -58,7 +58,9 @@ There are two ways to release a v2 (or higher) module version.
2. Update the `go.mod` file to include a `/v2` at the end of the module path. Tag the release with `v2.0.0`.
* To avoid confusion with this approach, consider putting the `v2.*.*` commits on a separate `v2` branch.
Packages are imported relative to the full module path: `import "me.io/mymod/v2/pkg1"` for package `pkg1` in module `me.io/mymod/v2`, or `import "me.io/mymod/pkg1"` for package `pkg1` in module `me.io/mymod` (v1 or v0).
Packages are imported relative to the full module path, for example:
* `import "me.io/mymod/v2/pkg1"` for package `pkg1` in module `me.io/mymod/v2`
* `import "me.io/mymod/pkg1"` for package `pkg1` in module `me.io/mymod` (v1 or v0).
### Version Selection
@ -120,7 +122,7 @@ To create a `go.mod` for an existing project, follow the following steps.
Day-to-day adding, removing, upgrading, and downgrading of dependencies should be done using 'go get', which will automatically update the `go.mod` file.
In addition, go commands like 'go build', 'go test', or even 'go list' will automatically add new dependencies as needed to satisfy imports (updating `go.mod` and downloading the new dependencies as needed).
In addition, go commands like 'go build', 'go test', or even 'go list' will automatically add new dependencies as needed to satisfy imports (updating `go.mod` and downloading the new dependencies).
To upgrade to the latest version for all transitive dependencies of the current module:
* run `go get -u` to use newer minor or patch releases