ruby.git/libexec/irb, branch v3_2_11

[ruby/irb] require_relative can't be used for default gems' exe files

2022-01-18T06:56:48+00:00

The `exe` folder and `lib` folder of default gems don't locate under the
same place. While `exe/irb` will be under the gem folder, `irb.rb` will be
under `lib/ruby/VERSION/`.

So `require_relative` will make `irb` unuseable when shipped with Ruby.

Related discussion in the comments: https://github.com/ruby/irb/pull/335

https://github.com/ruby/irb/commit/99d3aa979d

[ruby/irb] Use require_relative to require lib files

2022-01-17T05:23:40+00:00

1. `require` can mislead Ruby to load system irb's files and cause
   constant redefined warnings as other code loads the same module/class
   from lib folder.
2. Most files already use `require_relative`.

https://github.com/ruby/irb/commit/848d339f2e

[ruby/irb] Move IRB::TOPLEVEL_BINDING from exe/irb to lib/irb/workspace.rb

2021-09-09T21:37:07+00:00

https://github.com/ruby/irb/commit/e736a77076

[ruby/irb] Avoid loading files' local variables [Bug #17623]

2021-09-09T21:37:06+00:00

https://github.com/ruby/irb/commit/b12f0cb8e2

Use stub executables generated by RubyGems istead of original executables.

2018-11-25T01:20:00+00:00

It resolved the conflict issues when invoking `gem i rdoc` and the binstub
issues with Bundler and Rails.

  [Bug #5060][ruby-core:38257][Fix GH-2023]

  * https://github.com/rubygems/rubygems/pull/2338
  * https://github.com/heroku/heroku-buildpack-ruby/issues/829

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@65963 b2dd03c8-39d4-4d8f-98ff-823fe69b080e