From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Andrea Corallo via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: native-comp - Questions: eln-cache and subdirs.el? Date: Wed, 30 Sep 2020 10:51:39 +0000 Message-ID: References: Reply-To: Andrea Corallo Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29932"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Arthur Miller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 30 12:53:05 2020 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 1kNZjN-0007hf-1n for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Sep 2020 12:53:05 +0200 Original-Received: from localhost ([::1]:53188 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kNZjM-0003ep-0h for ged-emacs-devel@m.gmane-mx.org; Wed, 30 Sep 2020 06:53:04 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:52284) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kNZi8-00029E-W7 for emacs-devel@gnu.org; Wed, 30 Sep 2020 06:51:49 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:53143) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kNZi6-0000dX-Fp for emacs-devel@gnu.org; Wed, 30 Sep 2020 06:51:48 -0400 Original-Received: from mab (ma.sdf.org [205.166.94.33]) by mx.sdf.org (8.15.2/8.14.5) with ESMTP id 08UApdsa008819; Wed, 30 Sep 2020 10:51:39 GMT In-Reply-To: (Arthur Miller's message of "Wed, 30 Sep 2020 12:12:20 +0200") Received-SPF: pass client-ip=205.166.94.24; envelope-from=akrl@sdf.org; helo=mx.sdf.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/30 06:51:39 X-ACL-Warn: Detected OS = ??? 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.23 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:256747 Archived-At: Arthur Miller writes: > I have something like 3 different eln-caches now > > 28.0.50-x86_64-pc-linux-gnu-8e48a483af0cc5adcb56147eb760a39f > 2020-09-27 12:03 28.0.50-x86_64-pc-linux-gnu-cfb9403e84a6e99e5ac1bea6ab4abade > 2020-08-21 17:21 x86_64-pc-linux-gnu-958646d5fbcc566c > > Are they all used or I can delete some? I also see that not all files > are in all folders; Hi Arthur, if you have only one Emacs compiled you can always remove all of these but the most recent. Well technically you could also remove all of them and even eln-cache and it will recompile only what's needed in that case. > About subdirs: > > since Emacs deprecated subdirs; are there plans to get rid of that > mechanism later on, or it is it here to stay? I see in source code that > content of all subidirs.el is same (I checked few) on my machine; it > says: > > ;; In load-path, after this directory should come > ;; certain of its subdirectories. Here we specify them. > (normal-top-level-add-to-load-path '("eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" )) > ;; Local Variables: > ;; version-control: never > ;; no-byte-compile: t > ;; no-update-autoloads: t > ;; End: > > Since Emacs screams about deprecation when compiling; maybe this could > be saved into 'somefile.el' and then followed by a directory listing, or > just as assoc list? > > Example: > > ;; In load-path, after this directory should come > ;; certain of its subdirectories. Here we specify them. > ;; Local Variables: > ;; version-control: never > ;; no-byte-compile: t > ;; no-update-autoloads: t > ;; End: > ((dir1 . '(normal-top-level-add-to-load-path "eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" )) > (dir2 . '(normal-top-level-add-to-load-path "eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" )) > ( .... ) > (dirN . '(normal-top-level-add-to-load-path "eln-x86_64-pc-linux-gnu-600a7a2b93bc09d0" ))) > > Maybe I missunderstand how this set of subdirs is ment to be specified, > but maybe some similar mechanism is possible? Not sure I understand the interaction of subdirs with the native compiler. The system is meant to be transparent and the .elc are still there for now so any decision on this should not be influenced by the .eln machinery I think. Regards Andrea