From: deivid via ruby-core <ruby-core@...>
Date: 2024-09-13T17:44:08+00:00
Subject: [ruby-core:119185] [Ruby master Feature#20309] Bundled gems for Ruby 3.5

Issue #20309 has been updated by deivid (David Rodr�guez).


Regarding `irb`, I find it concerning that we need to add code like this: https://github.com/ruby/ruby/blob/9afc6a981deae6e23d938cf5c2c4baadfeaafdb1/prelude.rb#L12-L44. Those are internals of Bundler that are likely to break, and I can't even tell if that is doing what's intended?

The fact that we want `binding.irb` to work regardless of being in a `bundle exec` context or not feels like a sign that `irb` should probably stay as a default gem?

----------------------------------------
Feature #20309: Bundled gems for Ruby 3.5
https://bugs.ruby-lang.org/issues/20309#change-109767

* Author: hsbt (Hiroshi SHIBATA)
* Status: Assigned
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
I propose migrate the following default gems to bundled gems at Ruby 3.5. So, It means users will get warnings if users try to load them. 

(Update with 2024/03/14, 2024/06/05, 2024/09/06)

* rdoc(done)
  * We need to change build task like download rdoc gem before document generation.
    * extract `make doc` from `make all` and invoke `make doc` before `make install`.
      * done for Ruby 3.4
  * or We make document generation is optional from Ruby 3.5
    * We explicitly separate `make install` and `make install-doc`
* ostruct(done)
  * I make ostruct as optional on json at https://github.com/flori/json/pull/565 
* pstore(done)
* win32ole(done)
* logger(done)
  * activesupport needs to add logger to its dependency same as bigdecimal, drb or etc.
* fiddle(done)
* benchmark
* irb
  * We need to consider how works `binding.irb` after Ruby 3.5.
  * I consider to use `irb` without Gemfile. 
* reline
* readline (wrapper file for readline-ext and reline)

I have a plan to migrate the following default gems too. But I need to more feedback from other committers about them.

* io-console
  * rubygems uses that. Should we make optional that?
* open-uri
* yaml (wrapper file for psych)
  * syck is retired today. I'm not sure what people uses `psych` directly, not `yaml`.
* un
  * `ruby -run` is one of cool feature of Ruby. Should we avoid uninstalling `un` gem?
  * mkmf uses `ruby -run` for that. I need to investigate that.
* singleton
  * This is famous design pattern. Should we enforce users add them to their Gemfile?
* forwadable
  * `reline` needs to add forwardable their `runtime_dependency` after migration.
* weakref
  * I'm not sure how impact after migrating bundled gems.
* fcntl
  * Should we integrate these constants into ruby core?

I would like to migrate `ipaddr` and `uri` too. But these are used by webrick that is mock server for our test suite. We need to rewrite `webrick` with `TCPSocker` or extract `ipaddr` and `uri` dependency from `webrick`

Other default gems depend on our build process or other libraries deeply.  I will update this proposal if I could extract them from default gems.



-- 
https://bugs.ruby-lang.org/
 ______________________________________________
 ruby-core mailing list -- ruby-core@ml.ruby-lang.org
 To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org
 ruby-core info -- https://ml.ruby-lang.org/mailman3/lists/ruby-core.ml.ruby-lang.org/