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

No way to specify multiple version ranges? #10

Open
acoulton opened this issue Feb 17, 2017 · 0 comments
Open

No way to specify multiple version ranges? #10

acoulton opened this issue Feb 17, 2017 · 0 comments

Comments

@acoulton
Copy link

I have a cookbook that works fine with both the 5.x and 6.x versions of one of its dependencies. However, obviously it may or may not work with a future 7.x version. I want to allow projects that use my cookbook to update to the 6.x dependency version, but without introducing a breaking change to force them.

I thought I'd be able to specify > 5.1 <= 7.0 in some format, but it seems that there's no way to express that. I've tried various formats including arrays etc, but everything I try just gives did not contain a valid operator or a valid version string.

I appreciate it would be a nightmare to support arbitrary non-contiguous ranges, but it would be great to have basically a slightly-less-pessimistic constraint somehow. Apologies if this exists, but I can't find it documented or by trial and error.

acoulton added a commit to ingenerator/chef-duplicity-backup that referenced this issue Feb 17, 2017
Their breaking change doesn't affect us. Had to make the constraint
looser as per berkshelf/semverse#10 there
doesn't seem to be a way to specify >=5.1 <7.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

1 participant