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 am just trying out the goenv tool and wanted to check if there's an equivalent to the gvm pkgsets for isolating the package dependencies for different GoLang projects.
We can handle this by changing the GOPATH environment variable to the new Project workspace everytime we work on a project, but this is quite annoying.
Though Go has the official GoModules to isolate dependencies between projects, i think the pkgsets allows for complete isolation of the package and module dependencies by having a separate folders for projects sharing the same version of Go; this also allows programmers to switch between multiple Go Projects simultaneously without having to update GOPATH.
So, I would like to understand if such a thing is supported with goenv. I could not figure it out from the documentation. Please let me know if this is possible with goenv
Thanks
The text was updated successfully, but these errors were encountered:
I am just trying out the goenv tool and wanted to check if there's an equivalent to the gvm pkgsets for isolating the package dependencies for different GoLang projects.
We can handle this by changing the GOPATH environment variable to the new Project workspace everytime we work on a project, but this is quite annoying.
Though Go has the official GoModules to isolate dependencies between projects, i think the pkgsets allows for complete isolation of the package and module dependencies by having a separate folders for projects sharing the same version of Go; this also allows programmers to switch between multiple Go Projects simultaneously without having to update GOPATH.
So, I would like to understand if such a thing is supported with goenv. I could not figure it out from the documentation. Please let me know if this is possible with goenv
Thanks
The text was updated successfully, but these errors were encountered: