From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS4713 221.184.0.0/13 X-Spam-Status: No, score=-1.9 required=3.0 tests=AWL,BAYES_00, DKIM_ADSP_CUSTOM_MED,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,SPF_PASS, T_DKIM_INVALID shortcircuit=no autolearn=no autolearn_force=no version=3.4.0 Received: from neon.ruby-lang.org (neon.ruby-lang.org [221.186.184.75]) by dcvr.yhbt.net (Postfix) with ESMTP id EDAA0208CD for ; Wed, 16 Aug 2017 02:55:12 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 1ACF4120815; Wed, 16 Aug 2017 11:55:10 +0900 (JST) Received: from o1678916x28.outbound-mail.sendgrid.net (o1678916x28.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 05D51120810 for ; Wed, 16 Aug 2017 11:55:07 +0900 (JST) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=sendgrid.me; h=from:to:references:subject:mime-version:content-type:content-transfer-encoding:list-id; s=smtpapi; bh=fU9LO5GqJ94IPrFUKHsrWF4O710=; b=B1YqI01+HOh0Va3n7L CK6eY3nJaWryJv4OcBMVpmDRTrYbkCGJTSh7tjWDVKNDmqt21p3NvFG8Dp9zyqdQ Xu8XlYOnJxGwyusFpzi4q9o2eBmXj9GKnr4P0ztPrB6J2fhFjSp2f0Bw27V84HFa EuWtjg4bQ2PhQqZe+mtnmzVcE= Received: by filter0006p3mdw1.sendgrid.net with SMTP id filter0006p3mdw1-3666-5993B406-24 2017-08-16 02:55:02.990110712 +0000 UTC Received: from herokuapp.com (ec2-54-161-242-237.compute-1.amazonaws.com [54.161.242.237]) by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id i0QqsNrhT_yNEassSf32Qw Wed, 16 Aug 2017 02:55:02.928 +0000 (UTC) Date: Wed, 16 Aug 2017 02:55:03 +0000 (UTC) From: shevegen@gmail.com To: ruby-core@ruby-lang.org Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 57446 X-Redmine-Project: ruby-trunk X-Redmine-Issue-Id: 12733 X-Redmine-Issue-Author: hsbt X-Redmine-Issue-Assignee: hsbt X-Redmine-Sender: shevegen 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: ync6xU2WACa70kv/Ymy4QrNMhiuLXJG8OTL2vJD1yS7jpEcQeAPoMN0rJdAGPtjHWGV2OMx2c6apOh OWSbZNS2yha3RF37e2ELvuD0Y9EJvsWsNyAvek67CzfOxzt2ANg2+Zv/5Dxgqqq6vj8/vjTvaBcUzh YAeSKTn8sGT+T9hIcn2eTPvB3e+S2gdCwIvhTJJPI96WdZVD9s23reNVjg== X-ML-Name: ruby-core X-Mail-Count: 82395 Subject: [ruby-core:82395] [Ruby trunk Feature#12733] Bundle bundler to ruby core 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="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: ruby-core-bounces@ruby-lang.org Sender: "ruby-core" Issue #12733 has been updated by shevegen (Robert A. Heiler). I think that this is a pretty big undertaking, irrelevant of pros or cons to it (which surely exist). Bundler is popular, there is no doubt about this even though I myself do not use it - at https://rubygems.org/stats bundler is ranked #1 by a fair margin (rank #2 is multi_json and rank #3 is rake). Since I myself am not using bundler, I feel it would be unjust to comment on it pro or con, others can do so. But may I suggest something else, actually - gemify the remaining stdlib parts first before prioritizing on bundler integration into rubygems 3.x, which then will also be distributed with the next ruby releases? I am not sure what is missing aside from fileutils and strscan, if this is up to date (I am not sure, sorry; I thought there may be more but I can not find it right now - see the roadmap for 2.5 ... have there been any ruby core meetings in 2017? Probably have not been added to 2.5 or perhaps the meetings discussed past 2.5 situation). https://bugs.ruby-lang.org/projects/ruby-trunk/roadmap ---------------------------------------- Feature #12733: Bundle bundler to ruby core https://bugs.ruby-lang.org/issues/12733#change-66193 * Author: hsbt (Hiroshi SHIBATA) * Status: Assigned * Priority: Normal * Assignee: hsbt (Hiroshi SHIBATA) * Target version: 2.5 ---------------------------------------- rubygems team has plan to migrate bundler into rubygems at rubygems 3.0. ref. https://github.com/rubygems/rubygems/issues/1681 In current status, rubygems only use `Bundler` module on test suites. But we should track rubygems upstream step by step. I propose to bundle bundler for stdlib as default gem on ruby core repository. but we have some consideration. such as * bundler uses rspec for test suites. How to use rspec on ruby core repository? * Who are maintain bundler on ruby core repository? This issue is epic topic. Please comment your concerns or idea. -- https://bugs.ruby-lang.org/