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: Suppressing native compilation (short and long term) Date: Wed, 05 Oct 2022 10:39:08 +0300 Message-ID: <83lepuu3c3.fsf@gnu.org> References: <87bkqxf1ij.fsf@tethera.net> <8335c9dkyf.fsf@gnu.org> <83edvqafr7.fsf@gnu.org> <83h70m19yv.fsf@gnu.org> <87tu4mm7kt.fsf@trouble.defaultvalue.org> <87pmfa9k30.fsf@gnus.org> <83r0zqysyu.fsf@gnu.org> <877d1im5k3.fsf@trouble.defaultvalue.org> <83h70myrrp.fsf@gnu.org> <87r0zqknrx.fsf@trouble.defaultvalue.org> <83ill0yfct.fsf@gnu.org> <875yh0l9ya.fsf@trouble.defaultvalue.org> <835yh0vsv8.fsf@gnu.org> <87tu4jjdtq.fsf@trouble.defaultvalue.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="31255"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, emacs-devel@gnu.org To: Rob Browning Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Oct 05 09:48:34 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 1ofz8r-0007vL-Sq for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Oct 2022 09:48:34 +0200 Original-Received: from localhost ([::1]:49110 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofz8o-0006rY-IC for ged-emacs-devel@m.gmane-mx.org; Wed, 05 Oct 2022 03:48:31 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37494) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofyzo-0002H5-0p for emacs-devel@gnu.org; Wed, 05 Oct 2022 03:39:16 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:43196) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofyzm-0004QK-D5; Wed, 05 Oct 2022 03:39:10 -0400 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=00SeFZzhyRCfCCE6En1kYA9I6Gz15SQdGKml3INDtis=; b=juMw0dezsn9F k6jU93alUL22ZOAjRN/sv/ViF9FKe2NjNWZgqR18ZyS+VavNTVoqOI4+THFXxC0nwDF8Z9IP2FpIg E/TyqfGOL+ApH5F5a4Xrv+627guqyqE/CbTSR3zdrCLoyy8ofc7Ws3hWj2NE+d3tfYoQJKbsG8aBc vXNffcgGcW6Fr46kwb3SsH9garLSIoMl5F0+8ZkgpjS8Ia1/ZGJINMAUkInGpjBEYOSrWjWoNTB6J Mpk5nmFdDSbfaq7GL/MR66YVhrBDGaJQulMQ4iCZ1D5kiVfWDBMEightksVUp4scsOxTbPXPtm/ur YF3BDKDpkYWisYL9B5XplQ==; Original-Received: from [87.69.77.57] (port=4571 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 1ofyzl-0001zP-PA; Wed, 05 Oct 2022 03:39:09 -0400 In-Reply-To: <87tu4jjdtq.fsf@trouble.defaultvalue.org> (message from Rob Browning on Tue, 04 Oct 2022 19:48:01 -0500) 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:296946 Archived-At: > From: Rob Browning > Cc: larsi@gnus.org, yandros@gmail.com, tomas@tuxteam.de, emacs-devel@gnu.org > Date: Tue, 04 Oct 2022 19:48:01 -0500 > > Eli Zaretskii writes: > > > The above means (AFAIU) that disabling is not the right solution, > > because you want the *.eln files to go to the shared location where > > users could have them loaded when needed. Is that correct, or am I > > again missing something? > > If I understand you, I think the answer may be no? > > The test and package build cases are (often) isolated, automated, > debien-specific processes that happen on debian build machines (as root > and chrooted), and the entire workspace is then thrown away. It's never > relevant to a "normal" user. If the workspace is thrown away, you shouldn't care about the *.eln files it produces, right? They will be thrown away together with the workspace. So why bother disabling their production in this case? > The package install/upgrade process is system-wide, runs as root, and is > specifically and quite intentionally not per-user. It's intended to > establish the static, common baseline for *all* users on the machine > until the next package upgrade. When this package install/upgrade process runs, doesn't it include installing the *.eln files that come with the package, and need to be used when the users use the package after the installation? AFAIU, you want to install those *.eln files in a shared location, which is fine and supported: just put them in the same place under /usr/lib/emacs/VERSION/native-lisp/ directory where Emacs installs its precompiled *.eln files. Or, if you want to have the *.eln files from add-on packages to live in a separate place, define where that directory will be, install the package's *.eln files there, and tweak native-comp-eln-load-path to include that additional directory. Again, in this case as well, I see no problem with generation of *.eln files that you'd like to prevent. And yet you are still saying that disabling *.eln generation might be needed. Could you please describe in enough detail when are those unwanted *.eln produced in the two situations you described (test and package build case, and package install/upgrade case), and why are those *.eln files unwanted in that case? Thanks. P.S. I'm sorry to keep this thread alive for so long, but I really don't have a clear idea why you'd want to disable generation of *.eln files, and I think it's important for us to understand your reasons.