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.bugs Subject: bug#66554: [PATCH] Add the public API of Compat to the core Date: Sat, 13 Jan 2024 08:44:07 +0200 Message-ID: <83wmsdhgw8.fsf@gnu.org> References: <87pm1ggrdx.fsf@posteo.net> <87bk9scucg.fsf@daniel-mendler.de> <87y1cwpanh.fsf@posteo.net> <877ckgpa45.fsf@daniel-mendler.de> <87mstbpyd7.fsf@posteo.net> <87h6jjah1g.fsf@daniel-mendler.de> <87edenptba.fsf@posteo.net> <87bk9raaad.fsf@daniel-mendler.de> <87a5pbvbxc.fsf@posteo.net> <875xzza8jw.fsf@daniel-mendler.de> <87edemldlw.fsf@posteo.net> <83cyu6ifzw.fsf@gnu.org> <875xzyl8lq.fsf@posteo.net> <837ckeievw.fsf@gnu.org> <87h6jiqtsp.fsf@daniel-mendler.de> <835xzyiagj.fsf@gnu.org> <871qamkx0m.fsf@posteo.net> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="452"; mail-complaints-to="usenet@ciao.gmane.io" Cc: mail@daniel-mendler.de, stefankangas@gmail.com, monnier@iro.umontreal.ca, 66554@debbugs.gnu.org To: Philip Kaludercic Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sat Jan 13 07:45:31 2024 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1rOXlq-000AWz-OW for geb-bug-gnu-emacs@m.gmane-mx.org; Sat, 13 Jan 2024 07:45:30 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rOXlX-0007yr-5R; Sat, 13 Jan 2024 01:45:11 -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 1rOXlQ-0007yY-4t for bug-gnu-emacs@gnu.org; Sat, 13 Jan 2024 01:45:04 -0500 Original-Received: from debbugs.gnu.org ([2001:470:142:5::43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rOXlP-0000dz-El for bug-gnu-emacs@gnu.org; Sat, 13 Jan 2024 01:45:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1rOXlN-00059L-RL for bug-gnu-emacs@gnu.org; Sat, 13 Jan 2024 01:45:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sat, 13 Jan 2024 06:45:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 66554 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 66554-submit@debbugs.gnu.org id=B66554.170512827719748 (code B ref 66554); Sat, 13 Jan 2024 06:45:01 +0000 Original-Received: (at 66554) by debbugs.gnu.org; 13 Jan 2024 06:44:37 +0000 Original-Received: from localhost ([127.0.0.1]:38213 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rOXky-00058R-VS for submit@debbugs.gnu.org; Sat, 13 Jan 2024 01:44:37 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46202) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1rOXkw-00058B-2Y for 66554@debbugs.gnu.org; Sat, 13 Jan 2024 01:44:35 -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 1rOXkp-00005t-P8; Sat, 13 Jan 2024 01:44:27 -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=vdftRXMIA4KpDN5G7HtpaZdJFqPzvlMiw+XNKRQdcoc=; b=VL8d9yQeZxlw SZbckeZi8ign0pBmnxwMF5RC5LgYiR+RlxBDicWf1khAHbNfzQMx30mzYYNfGqPd2X0Nh5ztX2OaS JMkkjbObP3HT6iGy4HZ923gzn5l6AhQbmh2uye2Tp2K3O/dpNTOXhDc3yN56kEooG1m0xZMZyg0hR yKJomEdytIi/FnvJrKXBXS4hS9TRC8sdLYv3Szcm0dR2Q6CUScKdF16VE6KUu6S+lO3ZwEvwOk9m1 tAjBIhNAupskUGPYmT93bICxAdpT5fR/H8Gb8AYZN9CtblFCWhV1Ura7CG/KhZDxvErnW19HJELvr AcDowabjcLsWi0JEt9yFrA==; In-Reply-To: <871qamkx0m.fsf@posteo.net> (message from Philip Kaludercic on Fri, 12 Jan 2024 22:27:37 +0000) X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:278087 Archived-At: > From: Philip Kaludercic > Cc: Daniel Mendler , 66554@debbugs.gnu.org, > monnier@iro.umontreal.ca, stefankangas@gmail.com > Date: Fri, 12 Jan 2024 22:27:37 +0000 > > Eli Zaretskii writes: > > >> > I guess I'm misunderstanding something. The scenario that I have in > >> > mind is this: > >> > > >> > . we bump Emacs version to NN.1.90 as part of pretesting version NN.2 > >> > . as part of the pretest, some function changes that requires > >> > addition or change in compat.el > >> > . compat.el still claims version NN.1, although it includes changes > >> > not present in Emacs NN.1 > >> > > >> > Did I succeed in explaining my worries? > >> > >> I hope I understood your reasoning correctly. Shortly after you bump > >> NN.1.90 we can release compat-NN.2.0 which will include the necessary > >> change. > > > > Release where? on ELPA or as part of the Emacs tarball? > > > > And how do we make sure we will not forget to release this new version > > of compat.el? > > We have to distinguish the ELPA package Compat and the compat.el file > being added here. Yes, we should. I'm asking exactly that: when you say "we can release compat-NN.2.0", do you mean ELPA or do you mean compat.el in Emacs? > The ELPA package Compat is manually released on our > behalf, usually after a release of Emacs has been announced. The plan > is that the compat.el file does not have to be touched at all, since it > registers itself to use the right version, while Emacs is scraping the > for autoloads. So there shouldn't be any additional effort from the > side of Emacs maintenance, and nothing one can "forget". But that's exactly the problem I'm struggling with: compat.el in Emacs registers itself with inaccurate version, which lacks the last part after emacs-minor. As for "forgetting", I do mean whoever should remember to release a new version of Compat on ELPA -- if this is a manual operation, it can be forgotten, especially if it has to be related to pretest releases as well as the official releases. I guess I lack an overall picture of how this is supposed to work, as part of our pretest and release flow. Could you or someone else post such a complete description? Without this, I'm not sure I agree with the changes being considered, or at least don't quite understand their impact on the routine maintenance. Thanks.