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: 'go mod vendor' should not remove existing non-Go content from the vendor subdirectory #44119
Comments
This seems like a duplicate of #26366. |
No, that issue is concerned with impact on directories outside of |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
@bcmills @seankhliao I'm not sure current issue title is precise: "cmd/go: 'go mod vendor' should not remove existing non-Go content from the vendor subdirectory" |
To be clear: my intent was for If it insists on completely owning that directory, it needs to be configurable. |
Are there any updates related to this issue? It seems that there are no activities going on recently addressing this problem. This issue is still happening with go1.18.3. |
Tl;dr: Go is not the only tool I use in my project; I expect it share
vendor
peacefully.What version of Go are you using (
go version
)?(latest at the time of this writing)
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
What did you expect to see?
Ruby gems and Go modules "installed" in
vendor
.What did you see instead?
Only Go modules in
vendor
.Workaround
Bundler leaves Go modules alone, so re-running
bundle install
aftergo mod vendor
creates the desired state.The text was updated successfully, but these errors were encountered: