From: hsbt@ruby-lang.org
To: ruby-core@ruby-lang.org
Subject: [ruby-core:91717] [Ruby trunk Misc#15610] Could bundler & rubygems be shipped in site_ruby?
Date: Fri, 08 Mar 2019 11:54:12 +0000 (UTC) [thread overview]
Message-ID: <redmine.journal-76991.20190308115411.9086d334e32f73f4@ruby-lang.org> (raw)
In-Reply-To: redmine.issue-15610.20190218151116@ruby-lang.org
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: <mailto:ruby-core-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>
next prev parent reply other threads:[~2019-03-08 11:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <redmine.issue-15610.20190218151116@ruby-lang.org>
2019-02-18 15:11 ` [ruby-core:91583] [Ruby trunk Misc#15610] Could bundler & rubygems be shipped in site_ruby? deivid.rodriguez
2019-02-18 15:29 ` [ruby-core:91584] " shevegen
2019-02-18 18:36 ` [ruby-core:91586] " eregontp
2019-02-18 23:53 ` [ruby-core:91587] " hsbt
2019-03-08 11:54 ` hsbt [this message]
2019-03-22 15:32 ` [ruby-core:91938] " v.ondruch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=redmine.journal-76991.20190308115411.9086d334e32f73f4@ruby-lang.org \
--to=ruby-core@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).