New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cmd/go: document why go get module@none is interesting #26684

Open
nhooyr opened this Issue Jul 30, 2018 · 2 comments

Comments

Projects
None yet
3 participants
@nhooyr
Contributor

nhooyr commented Jul 30, 2018

Could not find any docs regarding this. What makes @none useful? Why would you want to just remove a package? Wouldn't your code still depend on it? Or is this only after you remove the usage of the package? And if so, wouldn't Go do this automatically on the next build?

@nhooyr

This comment has been minimized.

Contributor

nhooyr commented Jul 30, 2018

To be clear, this is a docs issue.

@bcmills bcmills modified the milestones: Go1.12, Go1.11 Aug 1, 2018

@rsc rsc changed the title from cmd/go: when would you want to use go get module@none? to cmd/go: document why go get module@none is interesting Aug 10, 2018

@rsc rsc modified the milestones: Go1.11, Go1.12 Aug 17, 2018

@rsc

This comment has been minimized.

Contributor

rsc commented Oct 25, 2018

Current text:

If a module under consideration is already a dependency of the current
development module, then get will update the required version.
Specifying a version earlier than the current required version is valid and
downgrades the dependency. The version suffix @none indicates that the
dependency should be removed entirely.

We could add to the last sentence:

... removed entirely, downgrading or removing modules depending on it as needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment