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: Sat, 05 Nov 2022 13:19:43 +0200 Message-ID: <835yft4pio.fsf@gnu.org> References: <87bkqxf1ij.fsf@tethera.net> <83sfk6ahty.fsf@gnu.org> <8735c6b0wo.fsf@gnus.org> <87y1ty9lha.fsf@gnus.org> <87lepym6ok.fsf@trouble.defaultvalue.org> <877d1i9h7k.fsf@gnus.org> <83edvqyr3q.fsf@gnu.org> <874jwl8e4p.fsf@gnus.org> <87pmf64beo.fsf@gnus.org> <87h70i4a46.fsf@gnus.org> <87czb648r9.fsf@gnus.org> <874jwi47l6.fsf@gnus.org> <87zgea2sgv.fsf@gnus.org> <83leop528p.fsf@gnu.org> <877d09u2rb.fsf@web.de> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18521"; mail-complaints-to="usenet@ciao.gmane.io" Cc: lekktu@gmail.com, larsi@gnus.org, akrl@sdf.org, rlb@defaultvalue.org, monnier@iro.umontreal.ca, david@tethera.net, emacs-devel@gnu.org To: "Dr. Arne Babenhauserheide" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Nov 05 12:20:27 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 1orHDu-0004ZJ-7i for ged-emacs-devel@m.gmane-mx.org; Sat, 05 Nov 2022 12:20:26 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1orHDV-00036L-LA; Sat, 05 Nov 2022 07:20:01 -0400 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 1orHDI-000351-DK for emacs-devel@gnu.org; Sat, 05 Nov 2022 07:20:00 -0400 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 1orHDH-0001c5-8E; Sat, 05 Nov 2022 07:19:47 -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=2xKtzfhHBqSoOxOQhevx7uC560mP1e1swlNeGXRjchQ=; b=LxEtGufKAr2p n+GCprjIsZRYb80H/pVJ8rUlqWlCzkHv7PjfL4dRhr89OxKIEcgLxsC7qWRlztueBRs2mAIoeVqWa OTCUYytRP+/R1WoLqVjJqYLdPrj9MkzPcHcKU5wWWQKSJFFClDqRP4dOOZEhH2R/gYYvwAISfVIv/ xfTBQaQbRR3we4766IK3v8OsoZ3vpSg4rjvI4rr9xJmbip0Z2/t9dyfqZm9cZ2+Z5kBejGvUpoRuY /IefzaRtIRMGrIwHNqiy9WsROzuxUTHIhQcwz+4vFLXkV0eNBTFblsQ74ZN0IchbfiOjSD6gVrOQq 27I3UfU/CUuBPwGSp4iZUw==; Original-Received: from [87.69.77.57] (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 1orHDG-0003iw-Hh; Sat, 05 Nov 2022 07:19:46 -0400 In-Reply-To: <877d09u2rb.fsf@web.de> (arne_bab@web.de) 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: , Original-Sender: "Emacs-devel" Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:299185 Archived-At: > From: "Dr. Arne Babenhauserheide" > Cc: Juanma Barranquero , larsi@gnus.org, akrl@sdf.org, > rlb@defaultvalue.org, monnier@iro.umontreal.ca, david@tethera.net, > emacs-devel@gnu.org > Date: Sat, 05 Nov 2022 11:12:10 +0100 > > Eli Zaretskii writes: > > >> In my setup, I call `startup-redirect-eln-cache' in init.el because I don't > >> want the cache in my .emacs.d/. > > > > Why do you need to do that? What's the problem with having the > > eln-cache under your ~/.emacs.d/? > > My ~/.emacs.d/ is actually versiontracked as part of my repository, > because emacs is my build tool to compile org-mode to PDF and I need a > reproducible environment so others can use it, too. > > During building, ~/.emacs.d/ is in the non-writable source directory > used by make distcheck. So what do you do with the *.elc files for the *.el files under ~/.emacs.d/? And anyway, I think your use case is very different from Juanma's, and is easily handled by customizing native-comp-eln-load-path.