-
Notifications
You must be signed in to change notification settings - Fork 223
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
dependency management #38
Comments
@mmlb pls post more details about this. |
I'm not sure what else to post apart from "vflow should be managing it's dependencies", here's
I'd be happy to sumbit a PR to add dep metadata files and make use of it in the makefile/dockerfile, I wanted to gauge if this was something that would be wanted. |
@mmlb it's not necessary, thanks! |
@mehrdadrad can you expand on why you think it is not necessary? If I build vflow today I have no guarantees that when I go to build it next month that it will build again. Both sarama-cluster and gopkg.in/yaml are at major version 2 which is evidence of this happening once before and possible in the future. |
Running
go get ./...
strikes me as not the greatest thing to be doing, any thoughts on using a package manager to handle the deps?I ran
dep init .
and found many of the dependencies to have sane versions released.The text was updated successfully, but these errors were encountered: