Skip to content
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

Jump to bottom

UX lacking for tools management with go mod #35494

Closed
mcandre opened this issue Nov 10, 2019 · 2 comments
Closed

UX lacking for tools management with go mod #35494

mcandre opened this issue Nov 10, 2019 · 2 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@mcandre
Copy link

mcandre commented Nov 10, 2019

This is the recommended way to track tools dependencies in Go involves parsing a tools.go:

https://marcofranssen.nl/manage-go-tools-via-go-modules/

That's a far cry from the tool management experience available today in Node.js, Python, and Ruby, where tools are already supported on par with libraries.

We could have a short term solution available very quickly, with some minor changes to the Go ecosystem to promote tools.go to an official standard:

  • golint, go vet, etc. would accept applications in imports.
  • go mod tidy would install any applications noted in tools.go.
  • go mod tidy and go install would improve support and documentation for specifying any custom build tags.

I'm not sure if tools.go is a long term strategy for tracking tools dependencies, but it's a start. Can we please get a better developer workflow than parsing Go code with awk?
@mvdan
Copy link
Member

mvdan commented Nov 11, 2019

There has been lots of discussion in this space in the last two years, such as #30515, #34506, and https://github.com/myitcv/gobin.

Is what you're suggesting a proposal? It seems a bit all over the place; for example, I hardly imagine go mod tidy will ever build or install anything. Also, golint doesn't play a part in the go tool.

If this is a proposal, it needs to take into account the previous work. If it's not a proposal, please clarify what exactly the issue is about.

@mvdan mvdan added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Nov 11, 2019
@gopherbot
Copy link

Timed out in state WaitingForInfo. Closing.

(I am just a bot, though. Please speak up if this is a mistake or you have the requested information.)

@golang golang locked and limited conversation to collaborators Dec 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mcandre @mvdan @gopherbot