Issue #20714 has been updated by Eregon (Benoit Daloze). I think the trouble is on `require 'fiddle'` in 3.4, e.g. in reline, it would actually succeed (and return true): ```ruby source 'https://rubygems.org' gem 'reline' ``` ``` $ bundle install $ bundle exec ruby -ve 'require "reline"; p Fiddle' ruby 3.4.0preview2 (2024-10-07 master 32c733f57b) +PRISM [x86_64-linux] Fiddle ``` If we remove the `$VERBOSE` changes in lib/reline/terminfo.rb: ``` $ bundle exec ruby -e 'require "reline"; p Fiddle' /home/eregon/tmp/reline-gemfile/vendor/bundle/ruby/3.4.0+0/gems/reline-0.5.11/lib/reline.rb:9: warning: fiddle was loaded from the standard library, but will no longer be part of the default gems starting from Ruby 3.5.0. You can add fiddle to your Gemfile or gemspec to silence this warning. Fiddle ``` So I think https://github.com/ruby/ruby/pull/11550 wouldn't solve that. ---------------------------------------- Bug #20714: Handle optional dependencies in `bundled_gems.rb` https://bugs.ruby-lang.org/issues/20714#change-110642 * Author: Earlopain (Earlopain _) * Status: Assigned * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: 3.3.5 * Backport: 3.1: UNKNOWN, 3.2: UNKNOWN, 3.3: UNKNOWN ---------------------------------------- I've encountered a few places around bundled gems where the library doesn't care if the gem is available, but will still provide some functionallity if it is. The way to accomplish that right now seems to be by setting `$VERBOSE = nil` and resetting it later again to not bother the user with the warning about the gem. However, this has the effect of silencing the warning about other gems as well, that may not be prepared about the bundling. From `ruby/reline` for example: https://github.com/ruby/reline/blob/c90f08f7e308d2f1cdd7cfaf9939fe45ce546fd2... Or the `logging` gem: https://github.com/TwP/logging/blob/df41715364f7eb8c65098cd3c3316677ef1f3784... I propose to simply delay the warning to the next require. GitHub PR at https://github.com/ruby/ruby/pull/11545 -- https://bugs.ruby-lang.org/