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: Tue, 04 Oct 2022 12:30:03 +0300 Message-ID: <835yh0vsv8.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> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18425"; mail-complaints-to="usenet@ciao.gmane.io" Cc: larsi@gnus.org, yandros@gmail.com, tomas@tuxteam.de, emacs-devel@gnu.org To: Rob Browning Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Oct 04 11:38:23 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 1ofeNb-0004cR-My for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 11:38:23 +0200 Original-Received: from localhost ([::1]:39014 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1ofeNa-000438-Kh for ged-emacs-devel@m.gmane-mx.org; Tue, 04 Oct 2022 05:38:22 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:38264) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofeFe-0003f9-Cz for emacs-devel@gnu.org; Tue, 04 Oct 2022 05:30:12 -0400 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:56580) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1ofeFd-0004gH-QP; Tue, 04 Oct 2022 05:30:09 -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=/bHRKba8LcUaY2mWGK/XmiggcFH21MLQoUwMInI95iY=; b=JhLbZRXqPIf/ skiuZo953lir4j8IwtSqMZQbt/D2uR9Xqh20Z2aW6EOAuRF6nwYblGqeOzhNpkEG+8nH9V/CC3Koi xftoJydv9rMmnHRG6TJhIWeii+cRYlWA8uU0ITd+PHcviSHkvIMzvA2VIiKBWxys98kzcAk5910wx C7nf1C68maH7IwiZW62pSeuC64Qgne2tMuQr2ZLtR8O5z6v8kjexqZMXONySGTWTrS9SEqAXqxi1w pl+FW0InqkpmDgXhjpulXPK2huQR44rGjyoz6OPlUghPd60KxLkPLWcbgwNewIJwEWPQs3Mv6b0J+ g8w75aGAlxcyXvSSSML3MA==; Original-Received: from [87.69.77.57] (port=1051 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 1ofeFb-00051K-Px; Tue, 04 Oct 2022 05:30:08 -0400 In-Reply-To: <875yh0l9ya.fsf@trouble.defaultvalue.org> (message from Rob Browning on Mon, 03 Oct 2022 19:16:29 -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:296867 Archived-At: > From: Rob Browning > Cc: larsi@gnus.org, yandros@gmail.com, tomas@tuxteam.de, emacs-devel@gnu.org > Date: Mon, 03 Oct 2022 19:16:29 -0500 > > Eli Zaretskii writes: > > > [Full disclosure: evidently, none of what I write below matters, so > > feel free to ignore.] > > Well, I can't speak for others, but it matters to me (your opinion and > the other upstream developers'), or I wouldn't be here, and I'm very > glad there's a "here for me to be" because I'm quite fond of Emacs :) I didn't mean you, FWIW. > > And I guess now I'm confused what is it exactly that you'd want to > > achieve. Do you want to disable native compilation, or do you want to > > have all *.eln files in a shared location? Because it seems to me you > > said you wanted both, and I don't see how both could be reconciled. > > The ability to disable .eln compilation entirely is only for some > Debian-specific (though maybe useful for others) special cases, not > anything we're proposing for "normal use". > > And it doesn't have to be "disabling" -- being able to redirect the .eln > files to another (temp) dir would be fine too, as long as it wasn't too > awkward to arrange for the entire (sub)process tree. > > Those special cases are (at least): > > - When building the relevant Debian packages -- for Emacs itself, for > add-ons like elpa-magit, etc. Debian forbids package builds from > writing outside of the package build directory /tmp, and another > tree or two, e.g. HOME is not allowed. Note that this is normally > handled by the Debian autobuilders, it's not something users > typically do. > > - During package installs, i.e. whenever Emacs is run during an "apt > install emacs" or "apt upgrade emacs", etc., and it may be run many > times there, both directly, and indirectly as it rebuilds whichever > packages need rebuilding (e.g. add-on packages). > > - During some autmated Debian tests. 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?