Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
cmd/go: why deprecate GOPATH just to add versioning? #27862
I really dislike the new module system, especially when running with
If adding versioning to achieve reproducible builds is desired, why not simply tweak the normal go build command just a little to make it try to find a file such as
Can someone explain why the current module system doesn't use the already cloned git repos in
I personally really like workspaces in go and I don't want them to go away. They're a nice place to store my go code, act as a repository for all the dependencies that I can quickly look at, and also hack (because they are in a predictable and intuitive path and not in damn zip files) without the need to checkout the repo again. They act as the root for all the import paths in a consistent, predictable and intuitive way without the need to make damn config files!
Also, I know that if I want to import an external package without fetching from a server I can use the
There is no need to reinvent the wheel or fix what isn't broken. If the importing system needs to be extended, extend it, use a new file, but just have it alter the behavior of the build command to checkout copies of repos from the workspace, please don't change the way the import path is resolved...
It only makes network requests for modules that are not already in the local cache.
If it allows arbitrary local edits within
See also #27542. And we're likely to make some improvements to