Skip to content
This repository was archived by the owner on Aug 23, 2023. It is now read-only.

Fix dep #1004

Merged
merged 7 commits into from
Aug 20, 2018
Merged

Fix dep #1004

merged 7 commits into from
Aug 20, 2018

Conversation

Dieterbe
Copy link
Contributor

No description provided.

* use master for code that we can easily keep track of, is unlikely to
  break something, or should be upgraded (e.g. leveldb has received
  some bugfixes)
* pin to whatever version or revision we were already using for the
  trickier dependencies
all users of upstream will have to
start using dep or vgo or something, not gopkg.in
@Dieterbe Dieterbe requested a review from woodsaj August 20, 2018 16:36
@Dieterbe Dieterbe mentioned this pull request Aug 20, 2018
Copy link
Member

@woodsaj woodsaj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

one of the benefits of using gopkg.in is that you can import 2 different versions a package.
We have relied on this in the past to handle migration from one raintank/schema version to another.

So this might pose a problem in future, but hopefully by then Go supports versioning within the import statements.

@Dieterbe Dieterbe merged commit cf08cbf into master Aug 20, 2018
@Dieterbe Dieterbe deleted the fix-dep branch September 18, 2018 09:09
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants