You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 9, 2020. It is now read-only.
Ugh. yes, your interpretation (and the tests) are correct. i must've fat-fingered those docs when i wrote them. sorry, and good catch! a PR would be awesome 🎉 🎉 🙇
What version of
dep
are you using (dep version
)?v0.3.2
What's the problem?
I'm having a hard time understand the How does
dep
decide what version of a dependency to use docs. Here's my interpretation of the ordering rules:master
for Git,default
for Mercurial, etc.), sorted lexicographically(?).What did you expect to see?
Given the slice example from the docs:
So, given a slice of the following versions:
Branch: master, devel
Semver tags: v1.0.0, v1.1.0, v1.1.0-alpha1
Non-semver tags: footag
Revision: f6e74e8
I'd expect the upgrade order to look like this:
[v1.1.0, v1.0.0, v1.1.0-alpha1, master, devel, footag, f6e74e8d]
What did you see instead?
[v1.1.0, v1.0.0, v1.1.0-alpha1, footag, devel, master, f6e74e8d]
Notice how the tag comes before the non-default branch, which itself comes before the default branch.
The tests relating to version ordering appear to match my interpretation (
eup
is the ordering):dep/internal/gps/version_test.go
Lines 9 to 68 in 8ddfc8a
I'm happy to do the PR!
The text was updated successfully, but these errors were encountered: