-
Notifications
You must be signed in to change notification settings - Fork 369
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
Add, update, and remove repository rules #56
Comments
The update-repos command can now add or update go_repository rules by import path. To use: gazelle update-repos example.com/repo1 example.com/repo2 This will automatically discover the remote, VCS, and latest commit for each repository containing the named packages. If a repository already exists in WORKSPACE, it will be updated in place. This functionality replaces wtool, which will be deleted soon after this lands. Related bazelbuild#56
The update-repos command can now add or update go_repository rules by import path. To use: gazelle update-repos example.com/repo1 example.com/repo2 This will automatically discover the remote, VCS, and latest commit for each repository containing the named packages. If a repository already exists in WORKSPACE, it will be updated in place. Related #56
I guess this will not come before vgo hits GA? |
Not sure what you mean by GA. The earliest vgo could possibly become the official Go build system is Go 1.12 (next winter). It will be shipped in the 1.11 SDK as an experimental tool. I'll get this functionality in as soon as I can, but there are a lot of things going on in parallel right now. We'll probably want more direct support for importing vgo mod files, too. |
Scratch GA. After GA, I think it will take a while before the vgo
versioning system is “generally adopted” ;-)
Jay Conrod <notifications@github.com>于2018年6月28日 周四下午10:24写道:
… Not sure what you mean by GA. The earliest vgo could possibly become the
official Go build system is Go 1.12 (next winter). It will be shipped in
the 1.11 SDK as an experimental tool.
I'll get this functionality in as soon as I can, but there are a lot of
things going on in parallel right now. We'll probably want more direct
support for importing vgo mod files, too.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#56 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAp9BzwGRIOasEqkC7fEDxRWrhdcW2Bwks5uBOcxgaJpZM4RNwik>
.
|
The link to the tool that adds repo rules to WORKSPACE doesn't appear to work anymore. The link is in this comment: bazelbuild/rules_go#295 (comment) What is the latest and greatest way to update the WORKSPACE with all my external dependencies automagically? :-) |
To get the transitive dependencies of an external package, I am thinking about the following:
I don't want to assume @jayconrod What do you think? |
@linzhp I'm not sure the Some more thought also needs to go into making this language agnostic. |
I agree that we should make this language agnostic by having each language extension implement how they get their dependencies and resolve the versions. But for Go, I don't see a big issue with the "go get" approach:
|
This is a catch-all issues for Gazelle repository rule management.
Gazelle will support an
update-repos
command. This will be able to:The text was updated successfully, but these errors were encountered: