Project

General

Profile

Feature #19351

Updated by hsbt (Hiroshi SHIBATA) about 1 year ago

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) 
 ``` 

 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 
 fiddle (C-ext) 
 ``` 

 Following gems also maintained by @kou, but they are used on RubyGems/Bundler or MJIT. RubyGems/Bundler. 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.

Back