From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-4.1 required=3.0 tests=BAYES_00,MAILING_LIST_MULTI, RCVD_IN_DNSWL_MED,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id C6EE520248 for ; Fri, 8 Mar 2019 11:54:19 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 9312312177A; Fri, 8 Mar 2019 20:54:16 +0900 (JST) Received: from o1678948x4.outbound-mail.sendgrid.net (o1678948x4.outbound-mail.sendgrid.net [167.89.48.4]) by neon.ruby-lang.org (Postfix) with ESMTPS id B0F16121740 for ; Fri, 8 Mar 2019 20:54:13 +0900 (JST) Received: by filter0002p3iad2.sendgrid.net with SMTP id filter0002p3iad2-8229-5C8257E4-5 2019-03-08 11:54:12.13246329 +0000 UTC m=+234185.436308683 Received: from herokuapp.com (unknown [3.87.251.236]) by ismtpd0012p1iad1.sendgrid.net (SG) with ESMTP id pSw4dmFvSV2uIuhuMP3NHw for ; Fri, 08 Mar 2019 11:54:12.097 +0000 (UTC) Date: Fri, 08 Mar 2019 11:54:12 +0000 (UTC) From: hsbt@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 67167 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 15610 X-Redmine-Issue-Author: deivid X-Redmine-Issue-Assignee: hsbt X-Redmine-Sender: hsbt X-Mailer: Redmine X-Redmine-Host: bugs.ruby-lang.org X-Redmine-Site: Ruby Issue Tracking System X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-SG-EID: =?us-ascii?Q?9+ToIm+BmphpEzrVEr2fqVDpB0VofQNbgfqsVvtPdY2wmdn2HtlxwzsST1bg1E?= =?us-ascii?Q?lMwMGFnWUt8Je=2FjKNexe0MB4ak7Ew7NigSbnd7Q?= =?us-ascii?Q?Dv0vVCwrWomDTxGKEB1D2Ak4HtQY7LvAXTqh69c?= =?us-ascii?Q?f6h3Stc0F2cGh8JyNee741Ag2X12lNDKTQpjx6f?= =?us-ascii?Q?VGgJOhZH7nB1ipLPyX8=2FsKSNVLMHMHf508Q=3D=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 91717 Subject: [ruby-core:91717] [Ruby trunk Misc#15610] Could bundler & rubygems be shipped in site_ruby? X-BeenThere: ruby-core@ruby-lang.org X-Mailman-Version: 2.1.15 Precedence: list Reply-To: Ruby developers List-Id: Ruby developers List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" 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=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: