Skip to content
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

Open
FroMage opened this issue Dec 15, 2011 · 12 comments
Open

Support more lax version schemes #7

FroMage opened this issue Dec 15, 2011 · 12 comments
Assignees
Milestone

Comments

@FroMage
Copy link
Member

FroMage commented Dec 15, 2011

1.0 or foo-beta for example. anything really

@ghost ghost assigned alesj Dec 15, 2011
@quintesse
Copy link
Member

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+
Also when running from the command line it would be nice if you could just give the name of the module and it will assume you want the latest version.

@FroMage
Copy link
Member Author

FroMage commented Dec 15, 2011

No idea, have to read the spec, but one thing experience shows is that number schemes are infinite, impenetrable and improperly used ;)

@gavinking
Copy link
Member

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.

@FroMage
Copy link
Member Author

FroMage commented Dec 17, 2011

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

@gavinking
Copy link
Member

Yes, much better!

@alesj
Copy link
Member

alesj commented Dec 18, 2011

For M2, hopefully. :-)

@FroMage
Copy link
Member Author

FroMage commented Jun 18, 2012

Looks like M4 :(

@alesj
Copy link
Member

alesj commented Jun 18, 2012

Version ranges bring a bunch of problems; it's a NP problem. ;-)
I'll see what can be done, but definitely not M3, hopefully M4 ...

@gavinking
Copy link
Member

Version ranges bring a bunch of problems

I agree. Personally I don't even see this as being on the roadmap for Ceylon 1.0.

@alesj
Copy link
Member

alesj commented Jun 18, 2012

For example; OSGi only recently properly addressed this issue - resolver is now part of the spec; after 10y+.
(of course it was already done before, but in a 1M diff ways)

@FroMage
Copy link
Member Author

FroMage commented Mar 6, 2013

M6.

@quintesse
Copy link
Member

1.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants