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
{{ message }}
This repository has been archived by the owner on May 6, 2022. It is now read-only.
dep is the "official experimental" dependency management tool for Go. I believe we should switch from using glide to vendor our dependencies to this tool.
From experience, the major benefit dep has over glide is that its usage is declarative. You run dep ensure and the tool does roughly the following:
looks at your imports
based on your imports, adds all the packages you need
based on your imports, removes all the packages you don't need
updates the dependencies file (Gopkg.toml), the lock file (Gopkg.lock), and the vendor directory as needed
The result is that we would no longer need to run glide get to manually add new dependencies. We've also had to do various manual tasks to manage our vendor directory. For example, we've had to rm -rf vendor and then re-run glide install to get a "clean" vendor directory. Dep provides the tools so we don't have to do that anymore.
The text was updated successfully, but these errors were encountered:
This seems to be where things are headed in the k8s community. I have heard good things about dep's dependency pruning capabilities and have found adding dependencies or updating a subset of dependencies to be extremely painful with glide. @carolynvs if you have the cycles, you're welcome to do this IMO
dep is the "official experimental" dependency management tool for Go. I believe we should switch from using glide to vendor our dependencies to this tool.
From experience, the major benefit dep has over glide is that its usage is declarative. You run
dep ensure
and the tool does roughly the following:Gopkg.toml
), the lock file (Gopkg.lock
), and the vendor directory as neededThe result is that we would no longer need to run
glide get
to manually add new dependencies. We've also had to do various manual tasks to manage ourvendor
directory. For example, we've had torm -rf vendor
and then re-runglide install
to get a "clean" vendor directory. Dep provides the tools so we don't have to do that anymore.The text was updated successfully, but these errors were encountered: