You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
vgo: import "example.com/hello" [/tmp/tmp.08BtAFjstf/hello]: no Go source files
As I understand it, there is no requirement for a Go module to contain source code; it could just be a parent of submodules.
I wonder whether this issue could/should be broadened to be "fully define semantics of vgo list" to include:
the fact vgo list should work where there are no source files
vgo list -t, or some super-powers version of it, should give one the ability to list versions across all major version numbers (because otherwise I need to know the latest major version number to do vgo list -t example.com/hello/vX
adding the -deps and -test flags from tip
whether vgo list should ever create a go.mod if it doesn't exist
whether vgo list should have a mode which doesn't try to do any resolution/downloading and instead errors in case something doesn't fully resolve, so that tools depending on its output don't block for potentially long periods of time, or barf on non-JSON output
.... others?
The text was updated successfully, but these errors were encountered:
"vgo list" is about packages and will remain so (remember, it will be "go list").
If there is no package in the current directory, complaining about that fact is correct. Note that vgo list -m . at the end of your script would work fine.
That said, there certainly are commands that are not about packages that complain incorrectly about "no Go source files" and we should fix them. That's not unique to list.
Let's make different issues for different list considerations. #25656 is for list -t. #25162 is for list and go.mod creation. #24066 is for list's use of the network.
I think that covers everything raised here, so I am going to close this issue.
Uh oh!
There was an error while loading. Please reload this page.
Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (
go version
)?vgo
version:Does this issue reproduce with the latest release?
Yes, and tip.
What operating system and processor architecture are you using (
go env
)?What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
What did you expect to see?
Something like:
What did you see instead?
As I understand it, there is no requirement for a Go module to contain source code; it could just be a parent of submodules.
I wonder whether this issue could/should be broadened to be "fully define semantics of vgo list" to include:
vgo list -t example.com/hello/vX
-deps
and-test
flags from tipvgo list
should ever create ago.mod
if it doesn't existvgo list
should have a mode which doesn't try to do any resolution/downloading and instead errors in case something doesn't fully resolve, so that tools depending on its output don't block for potentially long periods of time, or barf on non-JSON outputThe text was updated successfully, but these errors were encountered: