[ruby-core:107414] [Ruby master Feature#17873] Update of default gems in Ruby 3.1

Issue #17873 has been updated by retro (Josef Šimánek).


Eregon (Benoit Daloze) wrote in #note-38:
> Note: Whenever a gem is extracted from stdlib, we should be careful the gem can be installed on older Ruby versions, otherwise it's not possible for a library to depend on this newer gem via RubyGems (and it has to, otherwise `require` fails when using Bundler).
> See https://github.com/ruby/io-wait/pull/9#issuecomment-1026883889

In your comment, you're specifically asking that gem can be installed on EOL Ruby. I think that's worth discussion.

----------------------------------------
Feature #17873: Update of default gems in Ruby 3.1
https://bugs.ruby-lang.org/issues/17873#change-96313

* Author: hsbt (Hiroshi SHIBATA)
* Status: Closed
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
I promoted many standard libraries to the default gems. You can see them at https://stdgems.org/#default-gems-ruby-301

I propose the following libraries to promote the bundled gems from the default gems.

```
matrix
prime
net/ftp
net/smtp
net/pop
net/imap
```

They have primary maintainer in the canonical repository in github. So, they can release the new version with their convenience. 

@shugo @marcandre Any thought?

And I also propose to extract the following libraries from the default gems.

```
tracer
dbm
gdbm
```

They are no longer actively maintained and not widely used today.




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>