-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support more lax version schemes #7
Comments
Does that mean that we will always have to specify versions? Because this "anything" schema means I could never say module foo, version 2.0+ |
No idea, have to read the spec, but one thing experience shows is that number schemes are infinite, impenetrable and improperly used ;) |
Currently we do not support version ranges. At some stage in the future I suppose there will be a lot of pressure to do so, but for now it's easier to just not open up this can of worms. |
In fact what we can definitely do is detect the version if there is only one installed and list the existing versions in the error message if there are more than one |
Yes, much better! |
For M2, hopefully. :-) |
Looks like M4 :( |
Version ranges bring a bunch of problems; it's a NP problem. ;-) |
I agree. Personally I don't even see this as being on the roadmap for Ceylon 1.0. |
For example; OSGi only recently properly addressed this issue - resolver is now part of the spec; after 10y+. |
M6. |
1.0 |
1.0 or foo-beta for example. anything really
The text was updated successfully, but these errors were encountered: