Loosen version constraint for childprocess dependency #40
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.
I have an application that uses
childprocess (= 3.0.0)
. Trying to introducebrowsermob-proxy-rb (~> 0.3.1)
to that project produces a conflict becausebrowsermob-proxy-rb
declares a dependency onchildprocess (~> 0.5)
. To resolve the conflict, I can downgradechildprocess
, but I'd prefer not to. This project appears to be compatible with all versions ofchildprocess
from 0.5 to 3.0.0, so this change just loosens the version constraint in thegemspec
.If I remove the constraint in my
Gemfile
that I want the latest version ofbrowsermob-proxy-rb
,bundler
installs version 0.1.7 since that version had no constraint at all on thechildprocess
version. This is similarly undesirable.browsermob-proxy-rb/browsermob-proxy.gemspec
Line 19 in aa7e41f