Version dependencies

[AlekSi]

Use cases:

1. ..* – any version
2. X.. – major version X
3. X.Y.* – major X, minor Y, any patch
4. X.>=Y.* – major X, minor at least Y, any patch (X.>=0.* == X..)
5. X.Y.Z

Case 5 is typical for application, 4 – for nut.

[nevir]

Please consider semver style requirements, I'd be nice to avoid the Ruby gem issues that crop up due to overly restrictive requirements

~X.Y or ~X.Y.Z maybe?

[AlekSi]

Nuts use versioning schema adapted from SemVer. What is "semver style requirements"? Typical nuts will use X.. or 0.Y.*.

[nevir]

Mostly that you need some way of expressing a version requirement along the form of >= 1.2.0, < 2.0.0. I.e. "I depend on features introduced in 1.2.0"

And sometimes it's along the lines of >= 1.2.2, < 2.0.0 (i.e. "I depend on a bugfix found in 1.2.2")

[AlekSi]

It probably will be 1.>=2.* in the future.

[kavu]

And what about twiddlewakka ~>?

[nevir]

Please don't port ~> over directly, it's broken in its current form on the Ruby side of things. https://coderwall.com/p/wbljca

[kavu]

Hey, @nevir! A fair point! Thank you for this post!

[nevir]

~> is so close, too :P We just need an operator that does >= X.Y.Z && < (X+1).0.0 - $> maybe!

[AlekSi]

Updated issue description.