Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: restore ability to see what updates will happen #32039
In #26902, there was a very nice change that narrowed the set of updates that happen for things like
However, now it is not easy to see what those updates will be:
It would be nice if something could be done to make the "what updates are available" and "please do those updates" workflow more consistent and easy to remember.
Comments from CL 174099 discussion
It would be nice if there was some 'go list' invocation that could show the list of available upgrades under the new 'go get' behavior. One could try to do something today on tip by chaining together different commands, such as something like:
That might be close, but I am not sure if that is correct, and clearly that is not convenient.
Putting the above comments together-- it would be nice if there was a recommended way to do something like:
and have step 3. report no more upgrades are available. It would be nice if the same exact arguments could be used in each of those steps (although having them be the same arguments might not end up being possible or desirable based on other constraints).
For example, perhaps 'go list -u -m' could be defined in 1.13 to show the upgrades available under the new 'go get -u -m' behavior. That would mean you could do:
Alternatively, perhaps the meaning of 'all' for 'go list' could be made to conform to the newly narrower meaning meaning of 'all' for 'go get', and then you could do:
Or perhaps there could be some other change to smooth things out here.
Jay responded in CL 174099:
The exact behavior for
The “show what would happen” flag is usually
It might be reasonable to make
(Perhaps that's what
Given the freeze, it seems reasonable to defer this particular issue until 1.14, but it might be useful to make at least a preliminary decision on what the behavior here would be, especially as possibly related
Separately, today in 1.12,
To complicate matters,
I'd prefer a
It's unfortunate that these don't have the same name.
In any case, the new behavior is much closer to the GOPATH behavior, so I hope it won't be unacceptably slow.