On Monday, March 4, 2013 3:42:56 PM UTC+1, David Powell wrote: > > Version ranges aren't for communicating what versions of libraries you > have tested against - that is best done out-of-band. If you include a > version range, like the one above, you are saying that you want the > software to fail to build if something ends up requiring 1.5. This > probably isn't useful, as it will just lead to difficult to fix problems > for library consumers. >
The left-bounded, right-unbounded range seems to be the best practice since we always know the lowest acceptable version. > I guess the only time you might want a maximum version to be specified, is > if that version exists, and is known to be incompatible with your library. > Even here we shouldn't be too eager: only if the *official API* of a dependency acquires a breaking change should we use an upper bound; if there's just a single version out there that fails due to a bug, no action should be taken. -Marko -- -- 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.
