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

Better management of dependencies #87

Closed
otoolep opened this issue Apr 17, 2016 · 4 comments
Closed

Better management of dependencies #87

otoolep opened this issue Apr 17, 2016 · 4 comments

Comments

@otoolep
Copy link
Member

otoolep commented Apr 17, 2016

rqlite doesn't explicitly manage dependencies, and when a release is made, pulls in the dependencies in whatever state they are at. This is not ideal, and makes it difficult to reproduce a build.

@otoolep
Copy link
Member Author

otoolep commented Apr 28, 2016

With a move to Go 1.6, "vendoring" would probably be best.

@joonas-fi
Copy link

Current best practice is to use Dep [1]. It's really easy to use - I wish I started using it earlier because it was not as scary as I thought it would be. It's basically just $ dep init once to start using it and $ dep ensure at the beginning of your build process.

When Go modules mature (currently in beta), switch to using it.

[1] https://github.com/golang/go/wiki/vgo#current-state

For any production workloads, use dep, or migrate to it if you have not done so already.

@otoolep
Copy link
Member Author

otoolep commented Nov 2, 2018

Yes, I'm considering doing this for v5.0.

@otoolep
Copy link
Member Author

otoolep commented Jul 21, 2019

Done via 'go mod'.

See #563

@otoolep otoolep closed this as completed Jul 21, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants