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

select debugger gem dependent on ruby version #39

Closed
wants to merge 2 commits into from

Conversation

cruwe
Copy link

@cruwe cruwe commented Nov 11, 2016

pry-debugger depends on debugger, which cannot be installed on
ruby>=2.0. An extensive, lengthy and sometimes unnerving discussion can
be found on cldwalker/debugger#125

On May 16, 2014, cldwalker suggested moving to byebug for
rubies>=2. This is reflected in the change to Gemfile.

modified:   Gemfile

Thanks for your work on puppet-datacat! Cheers!

pry-debugger depends on debugger, which cannot be installed on
ruby>=2.0. An extensive, lengthy and sometimes unerving discussion can
be found on cldwalker/debugger#125

On May 16, 2014, cldwalker suggested moving to byebug for
rubies>=2. This is reflected in the change to Gemfile.

	modified:   Gemfile
@richardc
Copy link
Owner

This is blowing up some of the travis builds, as their bundler doesn't know what :mri_22 is.

Probably better to gate on RUBY_VERSION rather than use this platforms option, as it doesn't cope with expressions in the negative.

pry-debugger depends on debugger, which cannot be installed on
ruby>=2.0. An extensive, lengthy and sometimes unerving discussion can
be found on cldwalker/debugger#125

On May 16, 2014, cldwalker suggested moving to byebug for
rubies>=2. This is reflected in the change to Gemfile.

As it turns out, travisci has problems working with the mri platform
directive, so bacd782 has been
reworked to resort to simple if-else logic.
@cruwe
Copy link
Author

cruwe commented Nov 13, 2016

I am sorry to cause this hassle. I was under the impression that travis would deal with gem to ruby requirments differently. Apparently, sometimes builds fail choking on gems requiring ruby > 1.9.3 and I do not want to mess with your test setup. Interestingly, 139.9 got through, but I lack the travis expertise to really understand the issue. Please excuse the noise ...

@richardc
Copy link
Owner

It looks like you've hit some natural bitrot/bit shifting as json_pure (a transient dependency from puppet) has dropped support for ruby < 2.x too. I'll get that fixed up on master and then you can rebase your changes over mine.

@richardc
Copy link
Owner

I fixed up the rake and json_pure issues in #40 so if you can rebase this branch over master we should be testing just your changes (though there is no ruby 2.x in the travis matrix, so it might be worth extending that too)

@mxftw
Copy link

mxftw commented May 22, 2017

@richardc can you merge this PR into master?

@richardc
Copy link
Owner

I'm waiting on @cruwe rebasing, as per the preceding comment.

@richardc
Copy link
Owner

Stomped over this with #41 so closing

@richardc richardc closed this Jun 21, 2017
@cruwe
Copy link
Author

cruwe commented Jun 21, 2017

Oh gosh ... it totally escaped my notice that I had a task there. So sorry! In any case, thanks for your work!

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

Successfully merging this pull request may close these issues.

3 participants