[#111712] [Ruby master Feature#19322] Support spawning "private" child processes — "kjtsanaktsidis (KJ Tsanaktsidis) via ruby-core" <ruby-core@...>
SXNzdWUgIzE5MzIyIGhhcyBiZWVuIHJlcG9ydGVkIGJ5IGtqdHNhbmFrdHNpZGlzIChLSiBUc2Fu
14 messages
2023/01/07
[ruby-core:111934] [Ruby master Bug#18381] Default vs Bundled gems
From:
"hsbt (Hiroshi SHIBATA) via ruby-core" <ruby-core@...>
Date:
2023-01-20 11:33:38 UTC
List:
ruby-core #111934
Issue #18381 has been updated by hsbt (Hiroshi SHIBATA). I'll document this. ---------------------------------------- Bug #18381: Default vs Bundled gems https://bugs.ruby-lang.org/issues/18381#change-101362 * Author: vo.x (Vit Ondruch) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * ruby -v: ruby 3.1.0dev (2021-12-01 master 0b53a8895f) [x86_64-linux] * Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN ---------------------------------------- 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 -- https://bugs.ruby-lang.org/ ______________________________________________ ruby-core mailing list -- ruby-core@ml.ruby-lang.org To unsubscribe send an email to ruby-core-leave@ml.ruby-lang.org ruby-core info -- https://ml.ruby-lang.org/mailman3/postorius/lists/ruby-core.ml.ruby-lang.org/