Bug #18381: Default vs Bundled gems

• Status: Closed
• Assignee: hsbt (Hiroshi SHIBATA)
• Target version: -
• ruby -v: ruby 3.1.0dev (2021-12-01 master 0b53a8895f) [x86_64-linux]
• Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN

[vo.x (Vit Ondruch)]

Could there be documented what is the difference between default and bundled gems? E.g.

• Are the Bundled gems considered a part of StdLib or not?
• What is general strategy for the future, seeing more and more gems moving from default to bundled gems in Ruby 3.1
• Default gems does not need to be listed in Gemfile where Bundled gems needs to be listed in Gemfile
• Default gems can be used without RubyGems where Bundled gems requires RubyGems

[bkuhlmann (Brooke Kuhlmann)]

💡Not sure if this helps, but Ruby Standard Gems is always a great source of reference. I use it often, myself.

[hsbt (Hiroshi SHIBATA)]

• Status changed from Open to Assigned
• Assignee set to hsbt (Hiroshi SHIBATA)

[chooosen (Piotr Wasiak)]

:+1:

Documentation would solve probably my question about:
https://bugs.ruby-lang.org/issues/18400

[hsbt (Hiroshi SHIBATA)]

I'll document this.

[jeremyevans0 (Jeremy Evans)]

• Status changed from Assigned to Closed

This has been documented in doc/standard_library.rdoc.