-
Notifications
You must be signed in to change notification settings - Fork 654
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
Update golang.org/x/tools release and third-party "extra" patch #2556
Comments
I wonder if the extra patch could be made more robust by changing |
I'm confused about what's happening here exactly. You mentioned you're vendoring Overriding dependencies is the documentation for using alternate versions of repositories declared in About the extras patches: I don't want spend too much time automating generation of these: I'd rather avoid the need for them by fixing #2374. Unfortunately, that's still blocked on bazelbuild/bazel#11291. |
I'll update |
We have a setup where we basically drop a |
Seems like that should work. The patches will need to be applied manually, and they'll need to be updated for the version you're using, but I can't think of any other issues. |
Yup, for now I'm actually just applying a slightly altered version of the patch:
|
What version of rules_go are you using?
5ecc2d3
What version of gazelle are you using?
0.21.0
What version of Bazel are you using?
3.0.0
Does this issue reproduce with the latest releases of all the above?
Yes
What operating system and processor architecture are you using?
macOS Catalina
What did you do?
Vendor
golang.org/x/tools
at/past golang/tools@5c6ccfdWhat did you expect to see?
bazel build @org_golang_x_tools//...
works.What did you see instead?
The commit above refactored things by adding a couple new files (
bimport.go
andbexport.go
), which isn't reflected in https://github.com/bazelbuild/rules_go/blob/master/third_party/org_golang_x_tools-extras.patch.It'd be great to also include a README file in https://github.com/bazelbuild/rules_go/tree/master/third_party that explains how one might generate these patches (in particular, the "extra" patches), or a BUILD rules that can generate them automatically.
The text was updated successfully, but these errors were encountered: