Issue #15610 has been reported by deivid (David Rodrguez).

----------------------------------------
Misc #15610: Could bundler & rubygems be shipped in site_ruby?
https://bugs.ruby-lang.org/issues/15610

* Author: deivid (David Rodrguez)
* Status: Open
* Priority: Normal
* Assignee: 
----------------------------------------
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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>