From: deivid.rodriguez@... Date: 2021-05-28T10:24:02+00:00 Subject: [ruby-core:104081] [Ruby master Feature#17873] Update of default gems in Ruby 3.1 Issue #17873 has been updated by deivid (David Rodr�guez). This sometimes happens when `rubygems` loads a default gem too early before `bundler` has been setup. Then when user code loads the actual gem it uses the `$LOAD_PATH` setup by bundler instead of the default one, causing the double load. Up until now we always found ways to fix these issues by making usages of default gems inside `rubygems` as lazy as possible, but we're probably still loading `digest` too early. I'll have a look at this. ---------------------------------------- Feature #17873: Update of default gems in Ruby 3.1 https://bugs.ruby-lang.org/issues/17873#change-92255 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * 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: