-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
store dependencies' versions with godep #235
Conversation
If this sounds good to everyone, I can go ahead and update |
LGTM |
Yeah. Given the Cayley-as-a-library notion, this is probably the right net answer. |
Looks like |
I really should also write something for the docs, as changing a dependency requires executing |
Looks like godep was hanging on the tip build; likely related to tools/godep#206 |
Note also this recent post https://groups.google.com/d/topic/golang-nuts/G0HO7sEsIQQ/discussion Maybe we could hold off until a canonical dep file format is actually decided in the nuts thread I linked #234. |
If it wasn't for there being an issue with tip, I would argue that having this merged now hurts no one and only gives us the benefit of having reproducible builds until the Go team figures out what they want to do. I don't know how long it's going to take them, but I hope it's sooner rather than later. |
These dependencies can be loaded into your $GOPATH simply executing `godep restore`. This will allow builds to become reproducible, without getting in the way of those wanting to consume parts of the project's source code as a library.
Rebased into one commit. The issue with tip seems to be resolved now. |
LGTM
|
store dependencies' versions with godep
These dependencies can be loaded into your $GOPATH simply executing
godep get
. This will allow builds to become reproducible, withoutgetting in the way of those wanting to consume parts of the project's
source code as a library.
As per the discussion in #234.