Skip to content
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

Closed
jmcarp opened this issue Dec 13, 2017 · 3 comments
Closed

Manage dependency versions #5

jmcarp opened this issue Dec 13, 2017 · 3 comments
Labels

Comments

@jmcarp
Copy link
Contributor

jmcarp commented Dec 13, 2017

For users who don't deploy this app as a BOSH job, it would be useful to capture dependency versions using dep. Running go get ./... doesn't work at the moment because brokerapi vendors its dependencies, leading to conflicting copies of lager. I could grab the current dependency versions by checking out nfs-volume-release and copying its src directory to vendor or setting a custom GOPATH, but that feels like a hack.

Would you all be open to tracking dependencies with dep? I'd be happy to run dep init and send a patch 😃.

@cf-gitbot
Copy link

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.

@julian-hj
Copy link
Member

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 .envrc. If you just type direnv allow in the nfs-volume-release directory, then your GOPATH will get set when you cd into nfs-volume-release and unset when you cd back out.

@julian-hj
Copy link
Member

Closing this, as we have no plans to fix it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants