-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manage dependency versions #5
Comments
We have created an issue in Pivotal Tracker to manage this: https://www.pivotaltracker.com/story/show/153648285 The labels on this github issue will be updated when the story is started. |
Hey, sorry for the super slow response. My only hesitation here is that we don't like to have things in our code that we don't test in ci, and we already have many flavors of nfs build and deployment, so adding yet another one is a bit painful. By convention, because we use bosh for mostly everything (even for cf-pushing the broker) we treat nfs-volume-release as a GOPATH and just gather all the dependencies in the correct versions as git submodules. You should not have to set a custom GOPATH yourself, because we already do that in |
Closing this, as we have no plans to fix it. |
For users who don't deploy this app as a BOSH job, it would be useful to capture dependency versions using
dep
. Runninggo get ./...
doesn't work at the moment becausebrokerapi
vendors its dependencies, leading to conflicting copies oflager
. I could grab the current dependency versions by checking outnfs-volume-release
and copying itssrc
directory tovendor
or setting a customGOPATH
, but that feels like a hack.Would you all be open to tracking dependencies with
dep
? I'd be happy to rundep init
and send a patch 😃.The text was updated successfully, but these errors were encountered: