We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The old go get downloads and install the main package, so the binary is automatically created.
go get
The behavior seems invalid now in vgo.
If I run vgo get outside of go module directory like this
vgo get
$ vgo get github.com/someone/program
It raises error cannot determine module root; please create a go.mod file there
cannot determine module root; please create a go.mod file there
I know it is expected, but the old behavior was convenient way of install main packages.
So will it just not supported any more? Or maybe I am missing something?
The text was updated successfully, but these errors were encountered:
@kybin I think you want vgo install here
vgo install
Sorry, something went wrong.
@myitcv Thanks, but vgo install also not working if I run it outside of go module directory.
Sorry, I misunderstood the original post @kybin
vgo will only work within a module:
vgo
cd `mktemp -d` export GOPATH=$PWD echo 'module "rubbish.com/blah"' > go.mod vgo install github.com/cespare/reflex
In the meantime you need to use the go tool to do what you want.
go
When the functionality of vgo is merged into the main go tool, how the go tool should behave in this situation will be well defined.
I'll close for now because this is not expected to work in vgo, and let @rsc correct anything above or re-open in case that's necessary.
Ah, Okay. Thanks.
No branches or pull requests
The old
go get
downloads and install the main package, so the binary is automatically created.The behavior seems invalid now in vgo.
If I run
vgo get
outside of go module directory like thisIt raises error
cannot determine module root; please create a go.mod file there
I know it is expected, but the old behavior was convenient way of install main packages.
So will it just not supported any more? Or maybe I am missing something?
The text was updated successfully, but these errors were encountered: