Issue #20187 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Closed to Open @Eregon reverts my changes at `ruby/spec`. We shouldn't test bundled gems in `make check`. But he disagree it. The current task environment is not intentional behavior from https://github.com/ruby/ruby/pull/6130 I propose disable them again at https://github.com/ruby/ruby/pull/9960. I think bundled gems should keep testing their code in their repository, not ruby repository. We only test them with `make test-bundled-gems` for supporting development version of ruby interpreter. ---------------------------------------- Feature #20187: Bundled gems at Ruby 3.4 https://bugs.ruby-lang.org/issues/20187#change-106741 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- This ticket is for tracking bundled gems status at Ruby 3.4. I added warnings for bundled gems of Ruby 3.3 at https://bugs.ruby-lang.org/issues/19351 and https://bugs.ruby-lang.org/issues/19776. I started to extract(promote) target libraries to bundled gems. These are: * abbrev * base64 * bigdecimal * csv * drb * getoptlong * mutex_m * nkf * observer * resolv-replace * rinda * syslog -- https://bugs.ruby-lang.org/