On Monday, March 4, 2013 3:01:13 PM UTC+1, Meikel Brandmeyer (kotarak) wrote:
> > The range [1.2;1.5) means that the library was tested with 1.2 up to 1.4 > and - believing in semver - their patchlevel children. 1.5 (was at that > time) not released, yet. So compatibility couldn't be guaranteed. For me > this is a reasonable approach. Sure. It might work with 1.5. Everyone is > free to place an exclusion to help the system resolve the conflict. But you > must be aware you might run into trouble. > This resembles Java's checked exceptions: "the user should be warned"; in reality it just causes frustrations. Libraries break even when they are within the declared range: nobody can predict all the interactions. On the other hand, most of the time an upgrade wouldn't hurt, but is prevented by a defensive version range, and this actually breaks down the whole build due to a lower bound by another library. If a "feature" ends up having to be defused more often than it provides value, then it's not a feature. I second Chas' preference of "innocent until proven guilty" or, as you put it, "optimism". -- -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
