-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools: tag and delete refactor/rename, refactor/importgraph, go/buildutil, cmd/gomvpkg #69538
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
Related Issues and Documentation (Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.) |
Change https://go.dev/cl/614895 mentions this issue: |
Previously, the -tags flag used the obsolete buildutil.TagsFlag, which only affects the behavior of the obsolete go/loader. This change causes the -tags flag to affect go/packages in these three tools, as it should. Updates golang/go#69556 Updates golang/go#69538 Change-Id: Ie45c51c7fe04863dba00bc2f81b0a78f1c9bd0e3 Reviewed-on: https://go-review.googlesource.com/c/tools/+/614895 TryBot-Bypass: Alan Donovan <[email protected]> Reviewed-by: Michael Matloob <[email protected]> Auto-Submit: Alan Donovan <[email protected]> Commit-Queue: Alan Donovan <[email protected]>
This proposal has been added to the active column of the proposals project |
The proposal is to tag and delete x/tools/refactor/rename, x/tools/refactor/importgraph, x/tools/go/buildutil, and x/tools/cmd/gomvpkg. They'll continue to work as well as they do now, but we won't be updating them. These tools don't work with modules (importgraph and buildutil deeply assume GOPATH mode) and some are obsoleted by more modern functionality (rename and gomvpkg have equivalents in gopls). I see the three packages have a significant number of importers, especially buildutil. Perhaps unsurprisingly, many of these importers are in GOPATH mode. Given that these importers won't have version information, what exactly happens to them if we tag and delete these packages? (I'm not saying this should hold up the proposal, but I want to make sure we're transparent here.) @alandonovan plans to email golang-nuts@ just in case people are using these. |
It sounds like @alandonovan still needs to mail golang-nuts. |
This is now done. |
Based on the discussion above, this proposal seems like a likely accept. The proposal is to tag and delete x/tools/refactor/rename, x/tools/refactor/importgraph, x/tools/go/buildutil, and x/tools/cmd/gomvpkg. They'll continue to work as well as they do now, but we won't be updating them. |
No change in consensus, so accepted. 🎉 The proposal is to tag and delete x/tools/refactor/rename, x/tools/refactor/importgraph, x/tools/go/buildutil, and x/tools/cmd/gomvpkg. They'll continue to work as well as they do now, but we won't be updating them. |
While implementing this proposal:
I immediately realized that most of the logic is not in the cmd package but in the refactor/rename package, which has never worked with Go modules. Similarly, refactor/importgraph and go/buildutil have the same limitation. And cmd/gomvpkg is in a similar state to the (now deleted) cmd/gorename.
I propose to tag and delete all of them following a similar process.
(FWIW, the only seemingly valuable part of go/buildutil is TagsFlag, which doesn't actually work in conjunction with go/packages; one must use the syntax
gopackages -buildflag=-tags=... patterns...
.)The text was updated successfully, but these errors were encountered: