Remove version constraint from windows cookbook dependency #108
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Sorry for the delay. It took me a while to figure out the problem here - our application cookbook should define the version of the windows cookbook when/if we run into problems. |
|
👍 |
KAllan357
added a commit
that referenced
this pull request
Nov 19, 2013
Remove version constraint from windows cookbook dependency
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Without removing this constraint I can't use my existing recipes with the artifact cookbook - windows cookbook v1.11.0+ works with rubyzip gem v1.0.0+, which I'm already using. You cannot mix the latest windows cookbook with an older rubyzip gem and vice versa.