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
I expected no error message, just a carriage return, and I expected then to find that the repo had been installed in the specified folder.
What did you see instead?
go: cannot find main module; see 'go help modules'
I gather and hope that the behaviour os go get will change in go 1.12 but, as I have been asking for two weeks now, what are we supposed to do until then?
At the moment I have to do a git clone followed by a go mod int <supplier>/<repo> yet @rsc says that "Module-based go get works for me" https://twitter.com/_rsc/status/1034625354172981248 - but has also said that there is an issue and it has to be sorted for go 1.12#24250.
I know I'm not the only one with these questions, but unless I'm missing some very loud and clear messages, it does seem that the communication over these issues has been somewhat lacking.
The text was updated successfully, but these errors were encountered:
I have come up with what is a partial solution. It is a shell script which simulates the go get action. The idea is that one copies the git clone url from github.com and then runs gog.sh [⌘]v. Of course, with Github.com you can copy the git clone url with just a couple of keystrokes. One can then run go run, go build or go install as usual.
What version of Go are you using (
go version
)?go version go1.11 darwin/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?What did you do?
go get github.com/<supplier>/<repo>
What did you expect to see?
I expected no error message, just a carriage return, and I expected then to find that the repo had been installed in the specified folder.
What did you see instead?
go: cannot find main module; see 'go help modules'
I gather and hope that the behaviour os
go get
will change ingo 1.12
but, as I have been asking for two weeks now, what are we supposed to do until then?At the moment I have to do a
git clone
followed by ago mod int <supplier>/<repo>
yet @rsc says that "Module-based go get works for me" https://twitter.com/_rsc/status/1034625354172981248 - but has also said that there is an issue and it has to be sorted forgo 1.12
#24250.I know I'm not the only one with these questions, but unless I'm missing some very loud and clear messages, it does seem that the communication over these issues has been somewhat lacking.
The text was updated successfully, but these errors were encountered: