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.

Sign up for GitHub

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

Jump to bottom

"Top-most" dependencies are not (always) preferred to deps of deps #4

Open
yfyf opened this issue Jan 21, 2014 · 1 comment
Open

"Top-most" dependencies are not (always) preferred to deps of deps #4

yfyf opened this issue Jan 21, 2014 · 1 comment
Labels
bug

Comments

@yfyf
Copy link

yfyf commented Jan 21, 2014

Say I have app1, which depends on app2, which furthermore both depend on dep1.

I observed that if app1 specifies a constraint for the version of dep1's vsn, say >= 2.0.0, while dep2 only specifies a constraint >=1.0.0 and also a tagged refspec, then the refspec of dep1 as specified by app2 will be used, resulting in a failure to satisfies the top-most constraint by app1.

Basically this means that you can't override dependency versions in the presence of tagged refspecs even if the actual version constrains would be compatible for doing so.

/cc #1 @thijsterlouw @motiejus
@yfyf
Copy link
Author

yfyf commented Mar 6, 2014

duplicate of rebar/#222

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yfyf