-
Notifications
You must be signed in to change notification settings - Fork 617
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
Use Go Modules #2647
Use Go Modules #2647
Conversation
|
4ab8c50
to
e351243
Compare
Switching to "goMod" base branch since moving to go modules affects the make targets. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
any idea why we need to update quite a few vendor packages as part of the change? is there a way to keep them unchanged?
gomod automatically pins the same library versions from Gopkg, so it's not the library versions changing (I spot checked a few too). Im not sure why there are so many differences in the vendor/ directory. I know that godep and gomod both have their own algorithms for determining if a package is unused. It seems like godep is generally a bit more aggressive in pruning unused vendored code. If we want to use gomod I dont think there's any other option. You can't even leave it as-is and just avoid running |
Thanks for explaining @sparrc |
Summary
Use go modules
Implementation details
Testing
New tests cover the changes:
Description for the changelog
Licensing
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.