-
Notifications
You must be signed in to change notification settings - Fork 20k
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
package management: Plans to migrate to dep
?
#15145
Comments
We've switched dependency management quite a lot until we arrived at the current govendor setup that works for all corner cases. What would be the added value of |
couple reasons: a) It's going to be in the official golang toolkit. If those are not enough then perhaps it would be better to wait until it's more solidified. |
I don't mind switching to a "standard" tool once it's accepted as such. But we don't really have the capacity to experiment in this direction, and to debug any issues, hence why for the current moment I'd stick with our working system. But we should definitely revisit this once |
Sure. It makes sense to play conservatively here. Should we keep this open for a revisiting at a later date or close for now? |
We will migrate to anything else if
When this happens, the transition will be a no-brainer and we don't need to have an issue for it now. |
Any chance of migrating go-ethereum to using
dep
? Seeing as it's aiming to be the package manager to end all golang package management problems, seems it would be useful to begin utilizing it.Any objections to using it? Seems it's basically ready to rock...although the secp256k1 issues might create some issues in the short run.
https://github.com/golang/dep
The text was updated successfully, but these errors were encountered: