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: Permanently fix org versioning breakage during builds? Date: Sun, 24 Dec 2023 20:57:22 +0200 Message-ID: <83cyuvbf8t.fsf@gnu.org> References: <25989.50971.995591.385250@google.com> <87a5q0dc9m.fsf@localhost> <87edfbbyzm.fsf@localhost> <875y0n4px0.fsf@localhost> <87v88n3515.fsf@localhost> <87mstz34ec.fsf@localhost> <87jzp3344t.fsf@localhost> <87cyuv320s.fsf@localhost> <83mstzbfos.fsf@gnu.org> <87plyv1lbx.fsf@localhost> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="22858"; mail-complaints-to="usenet@ciao.gmane.io" Cc: joaotavora@gmail.com, raman@google.com, emacs-devel@gnu.org To: Ihor Radchenko Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Dec 24 19:57:46 2023 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 1rHTfV-0005ih-EY for ged-emacs-devel@m.gmane-mx.org; Sun, 24 Dec 2023 19:57:45 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rHTfI-0001ku-Du; Sun, 24 Dec 2023 13:57:32 -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 1rHTfE-0001kT-LM for emacs-devel@gnu.org; Sun, 24 Dec 2023 13:57:29 -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 1rHTfE-00087f-5U; Sun, 24 Dec 2023 13:57:28 -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=uDGNjQ2phdYCQBxqsI/pwVmMC237fC7kDxjixeDf3Vs=; b=sE9yR0QSupQE S1aCt9TbgIJMOG/Ef3bXT2MAltlKhpMvNE84ZyI+OAwhpi63l5vj+LRjHu7HrnCpaR6MdxgkLNxAP pQh9/GCzVfL4G4DNLYTBnud5buOKZLCj7YpCIdhd4VekLC8LRIA53XZPBKVxTdIbFD72Dtk17lZ3j I6xBq+Vl6xhwkgG3zYV7+wcp5NJRybj+h4fSeQ4YW5zoZMLslL4N3o8fVUzRvGmpGohGJmhfRfLYB E+oiBIRe7OlsO3TdLn4GlFvG8tNZsACEFgDjrgrIchkL303gP/hWvtndFDbqTocv+uPQjQtiv11CP 1u3AgETxYLM40c2DPanE+w==; In-Reply-To: <87plyv1lbx.fsf@localhost> (message from Ihor Radchenko on Sun, 24 Dec 2023 18:56:02 +0000) 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:314186 Archived-At: > From: Ihor Radchenko > Cc: joaotavora@gmail.com, raman@google.com, emacs-devel@gnu.org > Date: Sun, 24 Dec 2023 18:56:02 +0000 > > Eli Zaretskii writes: > > >> org-assert-version is the best we came up with. > >> If you know a concrete idea how to solve it differently, feel free to > >> share it. > > > > Why not just let things break when incompatible changes in Org macros > > are installed? We do that for any other Lisp file in the repository > > that defines macros used by other files. Why cannot Org do the same > > when it is compiled as part of the Emacs build? > > Org can. However, breaking Emacs builds is not the main purpose of > org-assert-version. The bigger problem I am trying to solve is obscure > breakage when people upgrade Org mode or mix built-in and newer Org mode > in their init files. I am talking specifically about what happens when Org is compiled as part of an Emacs build, using the Emacs Makefile's. You can keep your safeguards for the other situations, of course.