Issue #19351 has been updated by vo.x (Vit Ondruch). vo.x (Vit Ondruch) wrote in #note-1: BTW I don't think there would be that much fixing needed after all. E.g. if Rails console depends on IRB and Rails specified the dependency on IRB, Rails users would not need to do anything out of ordinary. But of course, the could be some exceptional handling for IRB. The only differences would be, that they would get faster IRB updates, which they won't notice ATM. ---------------------------------------- Bug #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-101290 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal We propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong optparse observable resolv resolv-replace rinda un fcntl nkf syslog win32ole ``` ### Additional works I also propose to promote some rails dependencies: ``` ostruct base64 irb rdoc tsort singleton delegate ``` and gems maintained by @kou ``` csv strscan fiddle stringio ``` But if we promote them to bundled gems, many of users need to add `gem "csv"` into their Gemfile. I'm considering to avoid this situation. Can we the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by byroot (Jean Boussier). Yeah, a few of these will need to be handled by rubygems/bundler. I believe that for instance `strscan` is used to parse the `Gemfile.lock`. Historically Bundler simply vendored the gems it needs, but not sure how it could do that since it has a C-ext part. I assume you notified bundler people? What do they think? ---------------------------------------- Bug #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-101298 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal We propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong optparse observable resolv resolv-replace rinda un fcntl nkf syslog win32ole ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 benchmark delegate drb forwardable ipaddr irb mutex_m ostruct rdoc singleton tsort weakref bigdecimal date(datetime) racc ``` and gems maintained by @kou ``` csv strscan fiddle stringio ``` But if we promote them to bundled gems, many of users need to add `gem "csv"` into their Gemfile. I'm considering to avoid this situation. Can we the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by kou (Kouhei Sutou). I'm OK with gems maintained by me. ---------------------------------------- Bug #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-101306 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * Priority: Normal * Backport: 2.7: UNKNOWN, 3.0: UNKNOWN, 3.1: UNKNOWN, 3.2: UNKNOWN ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal We propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong optparse observable resolv resolv-replace rinda un fcntl nkf syslog win32ole ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 benchmark delegate drb forwardable ipaddr irb mutex_m ostruct rdoc singleton tsort weakref bigdecimal date(datetime) racc ``` and gems maintained by @kou ``` csv strscan fiddle stringio ``` But if we promote them to bundled gems, many of users need to add `gem "csv"` into their Gemfile. I'm considering to avoid this situation. Can we the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by hsbt (Hiroshi SHIBATA). It makes to leave out-of-sync status with published gem like #18169. I'm checking ALL diffs and commits of ruby/* repos every day for resolving this issue after #18169 requests. Example for https://github.com/ruby/ruby/pull/7025. And we can add new maintainer easily different with ruby/ruby repo. In fact, `net-smtp`, `net-imap`, `rexml` and etc are maintained and released by maintainer's convenience. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-101484 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal We propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong optparse observable resolv resolv-replace rinda un fcntl (C-ext) nkf (C-ext) syslog (C-ext) win32ole (C-ext) ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 benchmark delegate drb forwardable ipaddr irb mutex_m ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) racc (C-ext) ``` and gems maintained by @kou ``` csv fiddle (C-ext) ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` stringio (C-ext) strscan (C-ext) ``` But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering to avoid this situation. Can we the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by hsbt (Hiroshi SHIBATA). No. some of commits conflicts usually. and some of people push `ruby/ruby` directly for fixing CI failure, not `ruby/*` repo. So, we are always out-of-sync status without my work. Because you didn't work release work of CRuby. Release team easily released [new version of CGI](https://www.ruby-lang.org/en/news/2022/11/22/http-response-splitting-i… without Ruby releases. Release team always spent over 6 hours with 5-6 people for security release of Ruby. We really hope to leave this hard work. I already work to merge JRuby code with JRuby team. I welcome your patch for TruffleRuby. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-101499 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal We propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv resolv-replace rinda un fcntl (C-ext) nkf (C-ext) syslog (C-ext) win32ole (C-ext) ``` Update: I removed `optparse` from above list. ``` optparse: Used by Ruby build process ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 benchmark delegate drb forwardable ipaddr irb mutex_m ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) racc (C-ext) ``` and gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering to avoid this situation. Can we the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by hsbt (Hiroshi SHIBATA). I prepared auto-sync for all of default gems. But it's sometimes failed and ruby/ruby to ruby/* is not available for it. I always pick them and manually push all of repos. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-101513 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal We propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv resolv-replace rinda un fcntl (C-ext) nkf (C-ext) syslog (C-ext) win32ole (C-ext) ``` Update: I removed `optparse` from above list. ``` optparse: Used by Ruby build process ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 benchmark delegate drb forwardable ipaddr irb mutex_m ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) racc (C-ext) ``` and gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering to avoid this situation. Can we the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by hsbt (Hiroshi SHIBATA). Description updated https://github.com/ruby/ruby/pull/7436 is working fine to load bundled gems without Gemfile declaration. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-103776 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal We propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) ``` Update: I removed `optparse` and `un` from above list. Because they are used by Ruby build process. ``` optparse un ``` Update 2: I also removed the following libraries. `resolv` and `fcntl` are used by test of Ruby internal like `test_io.rb`. And we don't have built process of C extension at Windows platform. I gave up to extract `win32ole` in this time. ``` resolv fcntl (C-ext) win32ole (C-ext) ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` drb mutex_m ``` Update: `delegate` is used by `tempfile`. We need to keep `delegate` as default gems for build process. and I added `reline` into above list. Update 2: The following libraries used by tests of `ruby/ruby` and other libraries like psych. I need to remove their dependency from `ruby/ruby`. ``` base64 benchmark forwardable ipaddr irb reline ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) ``` And gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering to avoid this situation. Can we introduce the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by hsbt (Hiroshi SHIBATA). I discussed this proposal in [Misc #19722: DevMeeting-2023-07-13](https://bugs.ruby-lang.org/issues/19722) * Ruby 3.3: * Warn for adding bundled gems of Ruby 3.3 to Gemfile when user load bundled gems without `gem 'foo'` in their Gemfile. We can add this warning logic into `kernel_require.rb` or `LoadError` or other place. * Also warn existing bundled gems was loaded without `gem 'foo'` of Gemfile. ex `net-smtp`, `rexml` etc. * Ruby 3.4: * Promote bundled gems. * Raise LoadError same as current behavior with warnings of Ruby 3.3. I withdraw a proposal of bypass $LOAD_PATH hack. I will proceed with above plan instead. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-103837 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal for Ruby 3.3.0-preview2 I propose the following libraries will promote default gems to bundled gems at Ruby 3.3.0-preview2 ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) base64 drb mutex_m csv ``` Other default gems depends on `make test-all` or other standard libraries. It's hard to promote in this time. And I submit a PoC of bypass feature for Bundler and bundled gems: https://github.com/rubygems/rubygems/pull/6811 This feature add `load_paths` defined by `Gem.bundled_gems` that is pair list of Gem name and version under the Bundler environment. This mean user can `require` bundled gems like `csv` without `gem "csv"` on Gemfile. And we need to warn like "'csv' is loaded without Gemfile, add "gem 'csv'" in your Gemfile" in `require` or other place. I have no idea how notice this yet. ---- ### Proposal I propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) ``` Update: I removed `optparse` and `un` from above list. Because they are used by Ruby build process. ``` optparse un ``` Update 2: I also removed the following libraries. `resolv` and `fcntl` are used by test of Ruby internal like `test_io.rb`. And we don't have built process of C extension at Windows platform. I gave up to extract `win32ole` in this time. ``` resolv fcntl (C-ext) win32ole (C-ext) ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 drb mutex_m ``` Update: `delegate` is used by `tempfile`. We need to keep `delegate` as default gems for build process. and I added `reline` into above list. Update 2: The following libraries used by tests of `ruby/ruby` and other libraries like psych. I need to remove their dependency from `ruby/ruby`. ``` benchmark forwardable ipaddr irb reline ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) ``` And gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` ### Follow-up feature But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering avoiding this situation. Can we introduce the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by deivid (David Rodríguez). Nice. The way I see it, this warning would ideally detect whether the gem was loaded by library code or application code. If loaded by application code, it would directly recommend to add `gem "foo"` to the Gemfile as the proper solution. If loaded by library code, it would recommend to bug library author to add the dependency to their gemspec, and adding `gem "foo"` to the Gemfile as a temporary workaround to remove the warning. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-103858 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal for Ruby 3.3.0-preview2 I propose the following libraries will promote default gems to bundled gems at Ruby 3.3.0-preview2 ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) base64 drb mutex_m csv ``` Other default gems depends on `make test-all` or other standard libraries. It's hard to promote in this time. And I submit a PoC of bypass feature for Bundler and bundled gems: https://github.com/rubygems/rubygems/pull/6811 This feature add `load_paths` defined by `Gem.bundled_gems` that is pair list of Gem name and version under the Bundler environment. This mean user can `require` bundled gems like `csv` without `gem "csv"` on Gemfile. And we need to warn like "'csv' is loaded without Gemfile, add "gem 'csv'" in your Gemfile" in `require` or other place. I have no idea how notice this yet. ---- ### Proposal I propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) ``` Update: I removed `optparse` and `un` from above list. Because they are used by Ruby build process. ``` optparse un ``` Update 2: I also removed the following libraries. `resolv` and `fcntl` are used by test of Ruby internal like `test_io.rb`. And we don't have built process of C extension at Windows platform. I gave up to extract `win32ole` in this time. ``` resolv fcntl (C-ext) win32ole (C-ext) ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 drb mutex_m ``` Update: `delegate` is used by `tempfile`. We need to keep `delegate` as default gems for build process. and I added `reline` into above list. Update 2: The following libraries used by tests of `ruby/ruby` and other libraries like psych. I need to remove their dependency from `ruby/ruby`. ``` benchmark forwardable ipaddr irb reline ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) ``` And gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` ### Follow-up feature But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering avoiding this situation. Can we introduce the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by deivid (David Rodríguez). Tricky, yes! I guess we could detect whether the caller lives inside a GEM_HOME or not to decide whether the caller is a library. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-103868 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal for Ruby 3.3.0-preview2 I propose the following libraries will promote default gems to bundled gems at Ruby 3.3.0-preview2 ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) base64 drb mutex_m csv ``` Other default gems depends on `make test-all` or other standard libraries. It's hard to promote in this time. And I submit a PoC of bypass feature for Bundler and bundled gems: https://github.com/rubygems/rubygems/pull/6811 This feature add `load_paths` defined by `Gem.bundled_gems` that is pair list of Gem name and version under the Bundler environment. This mean user can `require` bundled gems like `csv` without `gem "csv"` on Gemfile. And we need to warn like "'csv' is loaded without Gemfile, add "gem 'csv'" in your Gemfile" in `require` or other place. I have no idea how notice this yet. ---- ### Proposal I propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) ``` Update: I removed `optparse` and `un` from above list. Because they are used by Ruby build process. ``` optparse un ``` Update 2: I also removed the following libraries. `resolv` and `fcntl` are used by test of Ruby internal like `test_io.rb`. And we don't have built process of C extension at Windows platform. I gave up to extract `win32ole` in this time. ``` resolv fcntl (C-ext) win32ole (C-ext) ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 drb mutex_m ``` Update: `delegate` is used by `tempfile`. We need to keep `delegate` as default gems for build process. and I added `reline` into above list. Update 2: The following libraries used by tests of `ruby/ruby` and other libraries like psych. I need to remove their dependency from `ruby/ruby`. ``` benchmark forwardable ipaddr irb reline ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) ``` And gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` ### Follow-up feature But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering avoiding this situation. Can we introduce the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by deivid (David Rodríguez). I guess we can try to predict via codesearch which libraries will be affected by this and fix them in advance? ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-103871 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal for Ruby 3.3.0-preview2 I propose the following libraries will promote default gems to bundled gems at Ruby 3.3.0-preview2 ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) base64 drb mutex_m csv ``` Other default gems depends on `make test-all` or other standard libraries. It's hard to promote in this time. And I submit a PoC of bypass feature for Bundler and bundled gems: https://github.com/rubygems/rubygems/pull/6811 This feature add `load_paths` defined by `Gem.bundled_gems` that is pair list of Gem name and version under the Bundler environment. This mean user can `require` bundled gems like `csv` without `gem "csv"` on Gemfile. And we need to warn like "'csv' is loaded without Gemfile, add "gem 'csv'" in your Gemfile" in `require` or other place. I have no idea how notice this yet. ---- ### Proposal I propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) ``` Update: I removed `optparse` and `un` from above list. Because they are used by Ruby build process. ``` optparse un ``` Update 2: I also removed the following libraries. `resolv` and `fcntl` are used by test of Ruby internal like `test_io.rb`. And we don't have built process of C extension at Windows platform. I gave up to extract `win32ole` in this time. ``` resolv fcntl (C-ext) win32ole (C-ext) ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 drb mutex_m ``` Update: `delegate` is used by `tempfile`. We need to keep `delegate` as default gems for build process. and I added `reline` into above list. Update 2: The following libraries used by tests of `ruby/ruby` and other libraries like psych. I need to remove their dependency from `ruby/ruby`. ``` benchmark forwardable ipaddr irb reline ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) ``` And gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` ### Follow-up feature But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering avoiding this situation. Can we introduce the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/

Issue #19351 has been updated by deivid (David Rodríguez). Yeah, it probably makes sense to mention both possibilities and let the user figure out which one applies to her. ---------------------------------------- Feature #19351: Promote bundled gems at Ruby 3.3 https://bugs.ruby-lang.org/issues/19351#change-103909 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- In Ruby 3.2, the default gems and bundled gems are changed only adding `syntax_suggest`. I and some committers are considering promote default gems to bundled gems again for Ruby 3.3+. We hope to keep the current developer experience with dependency resolution and ignore the additional work like "Put gem "xxx" into your Gemfile" for developers. ### Proposal for Ruby 3.3.0-preview2 I propose the following libraries will promote default gems to bundled gems at Ruby 3.3.0-preview2 ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) base64 drb mutex_m csv ``` Other default gems depends on `make test-all` or other standard libraries. It's hard to promote in this time. And I submit a PoC of bypass feature for Bundler and bundled gems: https://github.com/rubygems/rubygems/pull/6811 This feature add `load_paths` defined by `Gem.bundled_gems` that is pair list of Gem name and version under the Bundler environment. This mean user can `require` bundled gems like `csv` without `gem "csv"` on Gemfile. And we need to warn like "'csv' is loaded without Gemfile, add "gem 'csv'" in your Gemfile" in `require` or other place. I have no idea how notice this yet. ---- ### Proposal I propose the following libraries will promote default gems to bundled gems at Ruby 3.3. They are not the dependencies of Rails and RubyGems/Bundler. ``` abbrev getoptlong observable resolv-replace rinda nkf (C-ext) syslog (C-ext) ``` Update: I removed `optparse` and `un` from above list. Because they are used by Ruby build process. ``` optparse un ``` Update 2: I also removed the following libraries. `resolv` and `fcntl` are used by test of Ruby internal like `test_io.rb`. And we don't have built process of C extension at Windows platform. I gave up to extract `win32ole` in this time. ``` resolv fcntl (C-ext) win32ole (C-ext) ``` ### Additional works I also propose to promote rails dependencies without rubygems/bundler deps: ``` base64 drb mutex_m ``` Update: `delegate` is used by `tempfile`. We need to keep `delegate` as default gems for build process. and I added `reline` into above list. Update 2: The following libraries used by tests of `ruby/ruby` and other libraries like psych. I need to remove their dependency from `ruby/ruby`. ``` benchmark forwardable ipaddr irb reline ostruct rdoc singleton tsort weakref bigdecimal (C-ext) date(datetime) (C-ext) ``` And gems maintained by @kou ``` csv ``` Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. Maybe, We couldn't promote them because RubyGems/Bundler couldn't bundle C-ext gems. ``` fiddle (C-ext): used by MJIT stringio (C-ext) used by RubyGems/Bundler strscan (C-ext) used by RubyGems/Bundler ``` ### Follow-up feature But if we promote them to bundled gems, many of users need to add like `gem "csv"` into their Gemfile. I'm considering avoiding this situation. Can we introduce the specific feature of bundled gems to RubyGems or Bundler? Example, bundler have allowed list for bundled gems. So, listed gems could be require without Gemfile under the bundle exec. -- https://bugs.ruby-lang.org/