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=-3.6 required=3.0 tests=AWL,BAYES_00, FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RCVD_IN_DNSWL_MED,SPF_HELO_NONE,SPF_PASS, UNPARSEABLE_RELAY 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 128C61F5AD for ; Sat, 11 Apr 2020 21:12:44 +0000 (UTC) Received: from neon.ruby-lang.org (localhost [IPv6:::1]) by neon.ruby-lang.org (Postfix) with ESMTP id 33C3E120BCF; Sun, 12 Apr 2020 06:12:18 +0900 (JST) Received: from xtrwkhkc.outbound-mail.sendgrid.net (xtrwkhkc.outbound-mail.sendgrid.net [167.89.16.28]) by neon.ruby-lang.org (Postfix) with ESMTPS id 33FC3120BCB for ; Sun, 12 Apr 2020 06:12:13 +0900 (JST) Received: by filterdrecv-p3iad2-8ddf98858-mzxhd with SMTP id filterdrecv-p3iad2-8ddf98858-mzxhd-20-5E9232BA-25 2020-04-11 21:12:26.524191263 +0000 UTC m=+1454700.622083231 Received: from herokuapp.com (unknown) by ismtpd0003p1iad1.sendgrid.net (SG) with ESMTP id lamK-HvLTkO6gmlQ93fmiA for ; Sat, 11 Apr 2020 21:12:26.451 +0000 (UTC) Date: Sat, 11 Apr 2020 21:12:26 +0000 (UTC) From: v.ondruch@tiscali.cz Message-ID: References: Mime-Version: 1.0 X-Redmine-MailingListIntegration-Message-Ids: 73597 X-Redmine-Project: ruby-master X-Redmine-Issue-Tracker: Misc X-Redmine-Issue-Id: 16778 X-Redmine-Issue-Author: deivid X-Redmine-Sender: vo.x 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?mWhqNvD1xlBozk4zn6CTHlnSPHlTKkyHJdiOH=2FzC52hXFyNqc+LRZKV=2FqL=2Fem8?= =?us-ascii?Q?ZcpusrraDbPV6pAofluOWTANfTm86WUo2LcdOxa?= =?us-ascii?Q?Qci4tGfUQjFAb6xyPfAD0b5yMTQd1GZyLHIbxV7?= =?us-ascii?Q?WUqWw9dD7dFz3a73Wv=2F0BDUx9QOms3YDlDmhkmO?= =?us-ascii?Q?1U=2FiNT8gIwU9gc8AdypU0bGBf63c2ADLMor1x1U?= =?us-ascii?Q?MJMKyPucL8mt7kxyw=3D?= To: ruby-core@ruby-lang.org X-ML-Name: ruby-core X-Mail-Count: 97836 Subject: [ruby-core:97836] [Ruby master Misc#16778] Should we stop vendoring default gems code? 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 #16778 has been updated by vo.x (Vit Ondruch). shevegen (Robert A. Heiler) wrote in #note-4: > this may help distributions such as, > say, debian, when there is some known bug already fixed, in a gem release, > and it can be quickly updated, without having to wait for e. g. x-mas = > release or pull out some patch manually. Wearing my Fedora Ruby maintainer hat, I was always for gemification of Std= Lib. Nevertheless, I can tell you that that the *current* design, including= the source tree layout, is going precisely against what I need to properly= maintain Ruby there. However, things has changed since the gemification started and the main cha= nge is that Ruby moved to Git. So I think it would be worth of considering = to use git submodules to get the gem source directories included into the R= uby sources, because AFAIK the concern was that Ruby developer want to have= the whole tree including the StdLib and they want to be able to commit eve= rywhere. The git submodules could solve that. ---------------------------------------- Misc #16778: Should we stop vendoring default gems code? https://bugs.ruby-lang.org/issues/16778#change-85058 * Author: deivid (David Rodr=EDguez) * Status: Open * Priority: Normal ---------------------------------------- Currently ruby-core vendors all the code in default gems, and runs the test= s for each of them. Also, ruby-core continuously updates the vendored code of default gems to s= ync with the upstream repos. That's overhead work, not only from syncronizi= ng the code itself, but it also requires perfect syncronization of releases= to avoid including versions of default gems that are different from releas= ed versions. Also, this causes confusion for contributors because the code lives "duplic= ated" in two different places. Some times contributors will open a PR in th= e ruby-core repo, only to find out that they need to go to the upstream rep= o and contribute it in there. And this rule is not even always followed and= sometimes ruby-core contributors apply patches to the vendored code direct= ly (many times to fix test-only issues inherent to the different structure = of the core repository). These patches then need to be contributed back to = the upstream repo. I believe that all of that kind of defeats the point of "gemification" of t= he standard library. Once some ruby code its gemified, it should be the new upstream's responsab= ility to make sure the code works and it's properly tested, and ruby-core s= hould be free'd from that responsability. Maybe ruby-core could do something along the following lines: * Remove all the vendored code from default gems. * When this code is needed for internal tests, manage it as a development d= ependency, clone it as necessary on non source controlled locations, and us= e it from there. * Maybe a file similar to `gems/bundled_gems` can be added for default gems= indicating their versions and upstream repos, to ease things. * Upon `make install`, clone the proper version of each default library and= get it installed in the default $LOAD_PATH. * Maybe add some bare high level CI checks to ensure that all default libra= ries can be properly required after `make install`, and that their executab= les (if they include any) can also be run. This should bring several benefits to the development process: * No more duplicated code. * No more syncronization from upstream to ruby-core. * No more syncronization from ruby-core to upstream. * No more confusion around the canonical place to contribute. * No more complexities derived from the different organization of the code = depending on whether it lives in ruby-core or outside. = I believe jruby already does something like this so it'd be interesting to = get some input from them. If this is a direction the ruby-core team would like to take, I'm happy to = help @hsbt with small steps towards slowly approaching to this high level g= oal. -- = https://bugs.ruby-lang.org/ Unsubscribe: