-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/tools/go/vcs: refresh from cmd/go #19362
Comments
@rsc, opinions on this? |
Reading .netrc seems a bit hacky. |
How is that hacky if the user who created the .netrc file ( Another (not even mutually exclusive) option would be to parse
|
It's hacky because it's not the go command's job to recreate the functionality of other tools. We're not reading .gitconfig and we're not reading .netrc, and that's good. That said, I think the go command itself handles bitbucketVCS just fine - for an auth failure it falls back to invoking git/hg directly, which is the perfect way to respect .netrc without parsing .netrc - and the x/tools/go/vcs copy is just out of date. Perhaps it is enough for someone to refresh the x/tools copy. |
... So govendor sync is calling the wrong X/tools function? |
No, I think x/tools/go/vcs (which is a copy of code internal to the go command) is out of date and needs to be updated. |
Perhaps the go command should vendor this library so that there is one version of this code to maintain? |
There will always be two copies to maintain. The go command is the primary source here. |
This just needs to be refreshed from the cmd/go master. |
I think go get should respect .netrc file at least while fetching meta-data. |
This package has been deprecated in #57051 and won't receive further development, so closing this as not planned. |
https://github.com/kardianos/govendor/issues/265 is due to
golang.org/x/tools/go/vcs/http.go
usinghttp.DefaultClient.get(privateBitbucketUrl)
without an Authorization header.bitbucketVCS
should extract the login and password from~/.netrc
The text was updated successfully, but these errors were encountered: