3 ms·
> Wouldn't this be less of an issue I'm not sure I understand what issue you would solve with using "[org.clojure/clojure ">1.2.0"]" compared to what we're doi
by diggan 7y ago
> Wouldn't this be less of an issue
I'm not sure I understand what issue you would solve with using "[org.clojure/clojure ">1.2.0"]" compared to what we're doing today, which is specifying the exact version we're using. What is the issue you're addressing here exactly?
In general, the Clojure community favors stability (more than others like npm) when it comes to dependencies, so you're almost always defining the exact version of the dependency you want.
- regularfry 7y agoThe exact issue I'm addressing is where a library wants to specify that it can only be used with a version of clojure later than 1.2.0 (in this case). The problem the author is talking about is when a library forces a language version on its users because it either specifies no version at all, or has to specify a specific one. I'm not sure I understand how `:scope "provided"` plays out if two dependencies say they want different versions of clojure, but that's also relevant.
- diggan 7y ago> I'm addressing is where a library wants to specify that it can only be used with a version of clojure later than 1.2.0 That sounds like a solution to some problem, but I'm unsure of what that problem is. Not sure it makes sense to depend on more than one version at a time, because you're usually just testing with one version and can ensure compatibility with just one version. Semver somehow made people believe that we can have versions numbers created with human-intuition but used as they are 100% true and generated by robots.
- regularfry 7y agoOh yeah, semver is mostly bunk. You can get most of what you need from a single incrementing version number. Look at it this way: say library A expresses a dependency on clojure 1.8, and library B on clojure 1.9. As the author of application C wanting to depend on both, what do I do when I want to use 1.10?