From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Rob Browning Newsgroups: gmane.emacs.devel Subject: Re: Suppressing native compilation (short and long term) Date: Sun, 02 Oct 2022 13:35:33 -0500 Message-ID: <87czbam5u2.fsf@trouble.defaultvalue.org> References: <87bkqxf1ij.fsf@tethera.net> <8335c9dkyf.fsf@gnu.org> <83edvqafr7.fsf@gnu.org> <83h70m19yv.fsf@gnu.org> <83czba17sb.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="28408"; mail-complaints-to="usenet@ciao.gmane.io" Cc: tomas@tuxteam.de, emacs-devel@gnu.org To: Eli Zaretskii , chad Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Oct 02 20:37:00 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 1of3pk-0007FG-3c for ged-emacs-devel@m.gmane-mx.org; Sun, 02 Oct 2022 20:37:00 +0200 Original-Received: from localhost ([::1]:38800 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1of3pi-000790-Sr for ged-emacs-devel@m.gmane-mx.org; Sun, 02 Oct 2022 14:36:58 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49864) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1of3os-0006Fu-SV for emacs-devel@gnu.org; Sun, 02 Oct 2022 14:36:06 -0400 Original-Received: from defaultvalue.org ([45.33.119.55]:37464) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1of3or-0007C9-HJ; Sun, 02 Oct 2022 14:36:06 -0400 Original-Received: from trouble.defaultvalue.org (localhost [127.0.0.1]) (Authenticated sender: rlb@defaultvalue.org) by defaultvalue.org (Postfix) with ESMTPSA id 5E3DF20174; Sun, 2 Oct 2022 13:35:34 -0500 (CDT) Original-Received: by trouble.defaultvalue.org (Postfix, from userid 1000) id 0C37314E081; Sun, 2 Oct 2022 13:35:34 -0500 (CDT) In-Reply-To: <83czba17sb.fsf@gnu.org> Received-SPF: pass client-ip=45.33.119.55; envelope-from=rlb@defaultvalue.org; helo=defaultvalue.org X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action 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" Xref: news.gmane.io gmane.emacs.devel:296678 Archived-At: Eli Zaretskii writes: > No, I don't think the similar handling makes sense here. The *.elc > files are architecture- and configuration-independent, whereas the > *.eln files are not. E.g., the same foo.elc could be used by user A > who runs Emacs 28 and by user B who runs Emacs 29. But the > corresponding *.eln files will be different, even though they were > produced from the same foo.el. Right, but for what it's worth, the Debian infrastructure is already set up to, and would, maintain separate .eln files/trees for those two cases, *if* we ever re-versioned the emacs packages. Right now, there's only one GNU Emacs flavor in debian, we don't provide versioned packages/flavors like emacs27 and emacs28 anymore. Though we could return to that again if it were ever deemed sufficiently valuable to people. -- Rob Browning rlb @defaultvalue.org and @debian.org GPG as of 2011-07-10 E6A9 DA3C C9FD 1FF8 C676 D2C4 C0F0 39E9 ED1B 597A GPG as of 2002-11-03 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4