Project

General

Profile

Feature #19351

Updated by hsbt (Hiroshi SHIBATA) almost 2 years 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 
 nkf 
 syslog 
 win32ole 
 ``` 

 ### Additional works 

 I also propose to promote some poromote 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.

Back