diff options
| author | David RodrÃguez <deivid.rodriguez@riseup.net> | 2025-07-10 09:36:08 +0200 |
|---|---|---|
| committer | Hiroshi SHIBATA <hsbt@ruby-lang.org> | 2025-07-14 11:52:13 +0900 |
| commit | 7dc284189a36b08e0eb8dcc2f5c7bdd3797b1394 (patch) | |
| tree | 85935fc54e100a60139ba2c236d3b814f8f6e28b | |
| parent | 55baf026ac2eaf9b9edb04b965dcb5e18c8badf9 (diff) | |
[rubygems/rubygems] Load RubyGems extensions in the first place
This is not currently causing any issues, but I think the most correct
thing to do is that Bundler loads the extensions to RubyGems in the
first place, so that they are available from the beginning.
https://github.com/rubygems/rubygems/commit/88faa5c7bb
| -rw-r--r-- | lib/bundler.rb | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/lib/bundler.rb b/lib/bundler.rb index d3219fe46e..761679ec8d 100644 --- a/lib/bundler.rb +++ b/lib/bundler.rb @@ -1,5 +1,6 @@ # frozen_string_literal: true +require_relative "bundler/rubygems_ext" require_relative "bundler/vendored_fileutils" require "pathname" require "rbconfig" @@ -7,7 +8,6 @@ require "rbconfig" require_relative "bundler/errors" require_relative "bundler/environment_preserver" require_relative "bundler/plugin" -require_relative "bundler/rubygems_ext" require_relative "bundler/rubygems_integration" require_relative "bundler/version" require_relative "bundler/current_ruby" |