Closed MSP-Greg closed 5 years ago
As of Ruby 2.6.0, both RubyGems & Bundler are included in the std-lib.
@BanzaiMan
Thank you. ruby-head now has the included versions of RubyGems & Bundler, and no warning are generated. I need to figure out why #55 didn't work, as the 'bundled gems' are still not included...
@BanzaiMan
Something has broken with gem installation in ruby-head/trunk.
I've got repo that logs info about the various Ruby versions/builds (https://travis-ci.org/MSP-Greg/travis-ruby/). For 2.6.0, it's set up exactly like the release is, same Rubygems, same Bundler, and same 'bundled gems' (rake, minitest, etc).
The fact that ruby-head/trunk is not is causing issues, especially with the warning from Object#=~
.
So, this PR and #55 were attempts to correct that. I ran CI in a repo, and it reported that it couldn't find rake
.
Since there's no 'build output' to the console, I'm not really sure what's happening...
EDIT: I'm mostly a windows type, so I'm not that familiar with rvm.
Thanks, Greg
never used it, as I build from the repo, but
https://cache.ruby-lang.org/pub/ruby/snapshot.tar.gz
contains all the gems
RubyGems 2.7.7 generates warnings when used with ruby-head/trunk. Due to
Object#=~
being deprecated...See https://travis-ci.org/MSP-Greg/travis-ruby/jobs/474206261#L999-L1003. The warnings appear on ruby-head, which has RubyGems 2.7.7, but not on Ruby 2.6.0, which (correctly) has RubyGems 3.0.1.
The additional output affects testing...