From: naruse@... Date: 2021-03-17T06:39:50+00:00 Subject: [ruby-core:102902] [Ruby master Feature#17684] Remove `--disable-gems` from release version of Ruby Issue #17684 has been updated by naruse (Yui NARUSE). At this time we just update `--help`. The conclusion of ruby core's discussion is * As the first step, let���s update the --help to explicitly state that --disable-gems is just for debugging * If rubygems startup becomes so fast in future, we can consider removal of --disable-gems (but still it is desirable for debugging) * Or someone who happen to report about --disable-gems again, we will consider again. We also discuss RubyGem accesses too many files in startup. We expect gem team improve that. https://gist.github.com/ko1/f0d8c899d580f7f69bb5608ab6d8215f ---------------------------------------- Feature #17684: Remove `--disable-gems` from release version of Ruby https://bugs.ruby-lang.org/issues/17684#change-90964 * Author: hsbt (Hiroshi SHIBATA) * Status: Closed * Priority: Normal ---------------------------------------- In my understand, `--disable-gems` is only debugging feature for ruby-core team. But some users enabled its option in test environment for performance or etc. So, `--disable-gems` option is wrong usage for some users. * https://github.com/rubygems/bundler/issues/7487#issuecomment-569901549 * https://github.com/rubygems/rubygems/pull/4440#issue-587031184 We should remove it from package version of ruby. -- https://bugs.ruby-lang.org/ Unsubscribe: