From: eregontp@... Date: 2021-05-20T11:01:01+00:00 Subject: [ruby-core:103914] [Ruby master Feature#17873] Update of default gems in Ruby 3.1 Issue #17873 has been updated by Eregon (Benoit Daloze). > And I also propose to extract the following libraries from the default gems. Those are already default gems. So I guess you mean no longer including them with Ruby, and `gem install NAME` would be needed to use them? Seems fine in general. I'm hesitant about `fcntl` since it's so small (just a bunch of constants) and I think it doesn't make so much sense to have that as a separate gem (it's already a default gem, though I don't see the point of that). ---------------------------------------- Feature #17873: Update of default gems in Ruby 3.1 https://bugs.ruby-lang.org/issues/17873#change-92044 * Author: hsbt (Hiroshi SHIBATA) * Status: Open * 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. ``` ostruct: matrix net/smtp net/ftp 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. ``` mutex_m tracer fcntl syslog prime ``` They are no longer actively maintained and not widely used today. -- https://bugs.ruby-lang.org/ Unsubscribe: