-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: go get -v is too verbose for repos with meta tags #23662
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
Comments
|
How many times have you found it useful for meta tags? |
Drive-by suggestion: have multiple levels of |
Not to start a flame war, but, after switching the majority of my development to Go, the only thing I miss about NPM is being able to know what I work from many offices, on planes and in coffee shops and knowing quickly if there's a problem adding packages is important for productivity. If the first download is going to be slow then the rest are too, and I need to get up and go find a better connection or I'll waste time. There have been many thread comments on this, and I'm not complaining, or piling-on. I'm really happy with Go- it's amazing. And that's why it deserves a first class package-add experience too. OK, my piece said, back to code.. |
This is absolutely still a problem but we didn't get to it for Go 1.11. |
Thank you for the confirmation. I expect with go mod this is a non-issue, I've not noticed any excessive logging since beginning to switch over. |
See also #26152. |
It's worth pointing out that niggling over the definition of |
I believe that is #15959. |
This comment was marked as off-topic.
This comment was marked as off-topic.
The deprecation of
|
Using
|
Inside a module, the example fails on one missing package. Removing the missing package adds the requested modules to go.mod with a short log.
|
Using |
This is interjected for every repo that uses meta tags. It would be useful if there were a failure only. Instead it disrupts the usual pattern of listing packages that have been consulted to fulfil the command. There are other ways to get this information a user can use if they were curious, or needed to debug the situation.
Here's a full sample of the noise in a typical circumstance:
The text was updated successfully, but these errors were encountered: