-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
cmd/go: install foo/v2 as binary "foo" #24667
Comments
Would there be support for installing multiple versions of |
I am not sure what the target Alternatively @adamdecaf would support for |
@myitcv Not really. I'm thinking more about being able to have a "foo v2" and "foo v3" binary around usable by programs wrapping the binary. No idea what I understand that the last execution of |
One option would be to install On the other hand, what is the use case for an installable module having a major version number in the vgo world? It looks like the semantic version is used to express API breakage for libraries, so it doesn't look like it's so important for installable modules, nor it does necessarily convey some usable information; so maybe the above suggestion is just over-engineering a non-problem. |
Binaries with conflicting names are not a new thing in vgo. You already have the problem with things like
Fundamentally you can only have one in your $PATH. Sorry. I believe solving this problem is out of scope for the go command generally. It's certainly out of scope for vgo. |
Sorry, I was replying to the earlier comment stream and forgot that was not the original issue. The original issue stands: we need to strip the /v2. |
What if the tool is actually called On a related note, how does the Go tool handle internal paths in relation to the GitHub user https://github.com/internal? The second questions is perhaps less serious, but the first one, I currently can't see how you'd differentiate between a tool actually being called |
Don't do that? But the module path should help to disambiguate, too: perhaps a binary package in subdirectory |
Purely hypothetical example though. |
Change https://golang.org/cl/128900 mentions this issue: |
If we're installing a binary with import path blah/blah/foo/v2, we should install it as foo, not v2.
The text was updated successfully, but these errors were encountered: