From: "hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@ml.ruby-lang.org>
To: ruby-core@ml.ruby-lang.org
Cc: "hsbt (Hiroshi SHIBATA)" <noreply@ruby-lang.org>
Subject: [ruby-core:116983] [Ruby master Feature#20309] Bundled gems for Ruby 3.5
Date: Tue, 27 Feb 2024 22:16:20 +0000 (UTC) [thread overview]
Message-ID: <redmine.issue-20309.20240227221620.572@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-20309.20240227221620.572@ruby-lang.org
Issue #20309 has been reported by hsbt (Hiroshi SHIBATA).
----------------------------------------
Feature #20309: Bundled gems for Ruby 3.5
https://bugs.ruby-lang.org/issues/20309
* 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.
* ostruct
* irb
* reline
* readline (wrapper file for readline-ext and reline)
* io-console
* logger
* fiddle
* pstore
* open-uri
* yaml (wrapper file for psych)
* win32ole
I have a plan to migrate the following default gems too. But I need to more feedback from other committers about them.
* rdoc
* We need to change build task like download rdoc gem before document generation.
* or We make document generation is optional from Ruby 3.5
* We explicitly separate `make install` and `make install-doc`
* un
* `ruby -run` is one of cool feature of Ruby. Should we avoid uninstalling `un` gem?
* 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/postorius/lists/ruby-core.ml.ruby-lang.org/
next parent reply other threads:[~2024-02-27 22:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-27 22:16 hsbt (Hiroshi SHIBATA) via ruby-core [this message]
2024-02-27 22:39 ` [ruby-core:116985] [Ruby master Feature#20309] Bundled gems for Ruby 3.5 rubyFeedback (robert heiler) via ruby-core
2024-02-28 8:46 ` [ruby-core:116990] " retro via ruby-core
2024-02-28 11:14 ` [ruby-core:116991] " Eregon (Benoit Daloze) via ruby-core
2024-02-28 11:18 ` [ruby-core:116992] " Eregon (Benoit Daloze) via ruby-core
2024-02-28 15:38 ` [ruby-core:116994] " jeremyevans0 (Jeremy Evans) via ruby-core
2024-02-28 17:21 ` [ruby-core:116997] " Eregon (Benoit Daloze) via ruby-core
2024-02-28 17:23 ` [ruby-core:116998] " Eregon (Benoit Daloze) via ruby-core
2024-03-14 9:44 ` [ruby-core:117153] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-03-14 10:41 ` [ruby-core:117158] " Eregon (Benoit Daloze) via ruby-core
2024-03-14 10:55 ` [ruby-core:117160] " hsbt (Hiroshi SHIBATA) via ruby-core
2024-03-14 14:58 ` [ruby-core:117176] " Eregon (Benoit Daloze) via ruby-core
2024-03-14 22:36 ` [ruby-core:117189] " hsbt (Hiroshi SHIBATA) via ruby-core
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.issue-20309.20240227221620.572@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
--cc=noreply@ruby-lang.org \
--cc=ruby-core@ml.ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).