From: hsbt@... Date: 2019-03-08T11:54:12+00:00 Subject: [ruby-core:91717] [Ruby trunk Misc#15610] Could bundler & rubygems be shipped in site_ruby? Issue #15610 has been updated by hsbt (Hiroshi SHIBATA). Status changed from Assigned to Rejected See https://bugs.ruby-lang.org/issues/15611#note-7 ---------------------------------------- Misc #15610: Could bundler & rubygems be shipped in site_ruby? https://bugs.ruby-lang.org/issues/15610#change-76991 * Author: deivid (David Rodr�guez) * Status: Rejected * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) ---------------------------------------- Currently bundler & rubygems are shipped together with the rest of the standard library (in `RbConfig::CONFIG["rubylibdir"]`). The fact that they share their folder with the rest of the standard library has caused some issues that wouldn't have happened if they were isolated. For example, https://bugs.ruby-lang.org/issues/15469 or https://github.com/rubygems/rubygems/issues/2188. Also, when you run `gem update --system`, rubygems installs a copy of itself and bundler in site_ruby, so you currently end up with two copies of different versions of bundler and rubygems in different folders of the $LOAD_PATH. @hsbt has fixed the above issues with a patch to bundler in https://github.com/bundler/bundler/pull/6941, but I still wonder whether it could be cleaner to ship them in site_ruby directly, so that `gem update --system` overwrites them and you always have a single default copy of both rubygems and bundler. Maybe this wouldn't be a good usage of site_ruby, and it's better to keep things as they are, but I figured I could ask ruby-core about it. Thanks for what you do! -- https://bugs.ruby-lang.org/ Unsubscribe: