On Mon, 2010-08-23 at 12:02 +0200, Ladislav Martincik wrote: > I think it makes sense as Yahuda Katz recommends [1] to switch from >= > to ~> whenever specifying Rubygems versions. I'm writing that because > I don't have CLA for doing any commits yet so maybe somebody else > could look at it. > > What do you think?
He's right in that '>=' can be disastrous because a release in the future might break API compatibility. We can't just go through and s/>=/~>/ though - because Ruby (or gems) has no real widely adopted versioning convention, it's anybody's guess whether releases 1.2.4 or 1.3.0 break API compat with 1.2.3. Therefore, you need to carefully examine each libraries habits, and decide whether it is safe to depend on = 1.2.3, ~> 1.2.3, or ~> 1.2 IOW, Ruby is a mess in this area (not that any of the other dynamic languages or Java are any better in that regard) David _______________________________________________ deltacloud-devel mailing list deltacloud-devel@lists.fedorahosted.org https://fedorahosted.org/mailman/listinfo/deltacloud-devel
