< :前の番号
^ :番号順リスト
> :次の番号
P :前の記事（スレッド移動）
N :次の記事（スレッド移動）
|<:前のスレッド
>|:次のスレッド
^ :返事先
_:自分への返事
>:同じ返事先を持つ記事（前）
<:同じ返事先を持つ記事（後）
---:分割してスレッド表示、再表示
| :分割して（縦）スレッド表示、再表示
~ :スレッドのフレーム消去
.:インデックス
..:インデックスのインデックス
Issue #15610 has been updated by vo.x (Vit Ondruch).
Just for completeness, this is my proposal:
https://bugs.ruby-lang.org/issues/5617
----------------------------------------
Misc #15610: Could bundler & rubygems be shipped in site_ruby?
https://bugs.ruby-lang.org/issues/15610#change-77270
* Author: deivid (David Rodr=EDguez)
* Status: Rejected
* Priority: Normal
* Assignee: hsbt (Hiroshi SHIBATA)
----------------------------------------
Currently bundler & rubygems are shipped together with the rest of the stan=
dard library (in `RbConfig::CONFIG["rubylibdir"]`). The fact that they shar=
e 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://bu=
gs.ruby-lang.org/issues/15469 or https://github.com/rubygems/rubygems/issue=
s/2188.
Also, when you run `gem update --system`, rubygems installs a copy of itsel=
f and bundler in site_ruby, so you currently end up with two copies of diff=
erent versions of bundler and rubygems in different folders of the $LOAD_PA=
TH.
@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 clean=
er to ship them in site_ruby directly, so that `gem update --system` overwr=
ites them and you always have a single default copy of both rubygems and bu=
ndler.
Maybe this wouldn't be a good usage of site_ruby, and it's better to keep t=
hings 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=3Dunsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>