Skip to content
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

Jump to bottom

cmd/go: doc: no official explanation about GOCACHE=off ? #25928

Closed
hirochachacha opened this issue Jun 17, 2018 · 3 comments
Closed

cmd/go: doc: no official explanation about GOCACHE=off ? #25928

hirochachacha opened this issue Jun 17, 2018 · 3 comments
Labels
Documentation FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Milestone
Go1.11

Comments

@hirochachacha
Copy link
Contributor

As far as I can see, I could not find the documentation about that.
@ianlancetaylor ianlancetaylor changed the title doc: no official explanation about GOCACHE=off ? cmd/go: doc: no official explanation about GOCACHE=off ? Jun 18, 2018
@ianlancetaylor ianlancetaylor added the NeedsFix The path to resolution is known, but the work has not been done. label Jun 18, 2018
@ianlancetaylor ianlancetaylor added this to the Go1.11 milestone Jun 18, 2018
@agnivade
Copy link
Contributor

@ianlancetaylor - How about adding something like this

You can set the variable to "off" if you want to bypass the cache

at the end of https://github.com/golang/go/blob/master/src/cmd/go/internal/help/helpdoc.go#L659, which is the output of go help cache.

@ianlancetaylor
Copy link
Contributor

@agnivade Sure, maybe at the end of the first paragraph that discusses GOCACHE.

@gopherbot
Copy link

Change https://golang.org/cl/119695 mentions this issue: cmd/go/internal: add a note about GOCACHE=off

@golang golang locked and limited conversation to collaborators Jun 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
Documentation FrozenDueToAge NeedsFix The path to resolution is known, but the work has not been done.
Projects
None yet
Milestone
Go1.11
Development

No branches or pull requests
4 participants
@hirochachacha @agnivade @ianlancetaylor @gopherbot