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
Many projects have screwed up go modules, and require a different dependency management tool, such as raw go get... with traditional GOPATH in order to function. Please allow at (@) notation to facilitate this. Otherwise, developers have to resort to a lot of twisted shell script just to manage Go dependencies.
The text was updated successfully, but these errors were encountered:
(You might ask: why not just add those things to GOPATH? The answer is: we did, and the result is Go modules.)
Many projects have screwed up go modules, and require a different dependency management tool
This statement is very broad and doesn't provide any references. What are these projects, and why is it that they require a different tool? It's not possible to investigate this issue without additional information.
If there's a specific issue with the cmd/go command that's preventing a specific project from using it, please file a new issue and provide details by filling in the template. We want to address such issues, and such a report would be very helpful.
The Go project doesn't use issue tracker for general discussion, please see golang.org/wiki/Questions for a list of better places to use.
Many projects have screwed up go modules, and require a different dependency management tool, such as raw
go get
... with traditionalGOPATH
in order to function. Please allow at (@
) notation to facilitate this. Otherwise, developers have to resort to a lot of twisted shell script just to manage Go dependencies.The text was updated successfully, but these errors were encountered: