From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Cutoff date for adding ruby-ts-mode? Date: Sat, 31 Dec 2022 08:31:17 +0200 Message-ID: <83cz805bka.fsf@gnu.org> References: <00b1ed5e-271b-fab7-cace-b6a04ac6fd46@yandex.ru> <83mt7571cu.fsf@gnu.org> <9fd271e5-5501-83de-0185-27a3c40eed26@yandex.ru> <83mt746d5z.fsf@gnu.org> <78ee732a-21a1-3443-2a0e-85343272e0ba@yandex.ru> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="32928"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org, pedz@easesoftware.com, monnier@IRO.UMontreal.CA To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Dec 31 07:32:14 2022 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pBVPh-0008Oo-KB for ged-emacs-devel@m.gmane-mx.org; Sat, 31 Dec 2022 07:32:13 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pBVP0-0003Am-BX; Sat, 31 Dec 2022 01:31:30 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pBVOo-0003AW-9D for emacs-devel@gnu.org; Sat, 31 Dec 2022 01:31:19 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pBVOn-0000kn-IW; Sat, 31 Dec 2022 01:31:17 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=WTO9z2+Mu8Ot+M9xst1LFI01vF+SqQIPjv6uCk5MPco=; b=qN5D3Dvtt4AB Jus55hXkxh5o2GrH+M+M2X+am0UeVX8shiC58LBB1rH0rNxov5EniBAhSogBKggg88IpgWi9hdpYt wMmg/oLAusp1NyZXIjw9Uw7klsKVcNp14h+pHdi+gSpY972s5d207QZqEkIrnzxQ7zUGFrjnJKXJY 9mU78PSkBxk7xlP3ycn+d6hwLILtuF66wyQvm2uZVfa00MT5F6NlilSEGemDvsHlLNJdWeVIecla/ vMkM0JB9mls3zC96NBH+rpq+Y41ezz+PC9hpgeAEelj7QP/Wnu50dzxAiCaTJ8roPWDyoupuPbkxy soxKzsEKhvGEqPTTYpXTZA==; Original-Received: from [87.69.77.57] (helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pBVOm-0000KK-HJ; Sat, 31 Dec 2022 01:31:16 -0500 In-Reply-To: <78ee732a-21a1-3443-2a0e-85343272e0ba@yandex.ru> (message from Dmitry Gutov on Fri, 30 Dec 2022 23:42:50 +0200) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:302147 Archived-At: > Date: Fri, 30 Dec 2022 23:42:50 +0200 > Cc: emacs-devel@gnu.org, pedz@easesoftware.com, monnier@IRO.UMontreal.CA > From: Dmitry Gutov > > >> Alternatively, we break from the common scheme and put the modes in > >> separate files, one depending on the other. Then they'll have to be > >> separate GNU ELPA packages (I think), and we'll need to synchronously > >> bump version and required-version in them every time when making > >> interrelated changes in the future. > > > > I'd prefer this alternative for now (modulo the separate ELPA packages > > part, which I leave for you to decide: they could also be a single > > package from my POV). If nothing else, having separate files is > > similar to what at least some other *-ts-mode's do. When we revisit > > these issues in the future, we'll be able to make the decisions about > > all of them. > > Okay. > > I wonder what's going to happen if we release Emacs 29 with ruby-mode > and ruby-ts-mode in separate files, and then later add a package called > 'ruby' to ELPA with ruby.el containing both modes. The ELPA package could also include 2 files, one for each mode. > Will the autoloads file from an ELPA package always take priority over > the built-in autoloads? If yes, then we don't have to do anything now. > Hopefully that's not undefined behavior. > > Alternatively, it would be possible to release two files as one ELPA > package, but it would seem to require a third file: one matching the > package name, ruby.el. I'll leave this part of the issue to Stefan and others who know more than I do about ELPA packaging.