Issue #19351 has been updated by hsbt (Hiroshi SHIBATA).
So maybe that automatic cherry-picking is only in one
direction, not the other, and maybe only for some gems and not all?
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/