-
Notifications
You must be signed in to change notification settings - Fork 19
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
Fix version aliases #71
Comments
Good catch, I'll add support for
clj-nix/test/cljnix/core_test.clj Line 102 in 3dffacf
What's the difference between version ranges and version patterns? I'm not familiar with I tried to add support for version ranges, but they are quite tricky. Here I have an example for version ranges, but it's quite hacky (for an old Anyways, given that I think version ranges are a bad idea, and how much time I already |
I think I was confusing with exclusion wildcards please disregard.
Ack. Do you think we can make this case work: A transitive dependency has a version range, which gets overridden by a "closer" dependency with a regular version? Right now, that errors. Maybe unsupported version expressions could be demoted to a warning, and assumed to be provided otherwise? |
I think that was the case building While I don't plan to work on this, if you find a solution, I'm happy to help with a PR. |
Interesting, I'll try that workaround. In the mean time, I may have a go at this at some point. But no promises either, I didn't end up needing that transitive dependency, for now. |
deps.edn allows to use version aliases, like
RELEASE
orLATEST
.For deps cache, clj-nix resolves these to versions, without keeping the original alias resolvable.
Test case
There are similar differences in given and used version for
[1.4,1.6)
*
The text was updated successfully, but these errors were encountered: