[#104004] [Ruby master Feature#17883] Load bundler/setup earlier to make `bundle exec ruby -r` respect Gemfile — mame@...
Issue #17883 has been reported by mame (Yusuke Endoh).
21 messages
2021/05/24
[ruby-core:103930] [Ruby master Feature#17873] Update of default gems in Ruby 3.1
From:
marcandre-ruby-core@...
Date:
2021-05-21 04:34:57 UTC
List:
ruby-core #103930
Issue #17873 has been updated by marcandre (Marc-Andre Lafortune). Thanks, I agree about `prime`. I imagine `matrix` users are limited and will be ok. I'm not sure about `ostruct`. Could we consider to bundle them in next major version but with some warning? If you "update" the gem then the conversion warning would not be there. This could ease conversion. ---------------------------------------- Feature #17873: Update of default gems in Ruby 3.1 https://bugs.ruby-lang.org/issues/17873#change-92060 * 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. ``` ostruct: matrix net/smtp net/ftp net/pop net/imap prime ``` 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 syslog ``` They are no longer actively maintained and not widely used today. -- https://bugs.ruby-lang.org/ Unsubscribe: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe> <http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>