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: Dedicated search path variable for architecture-dependant loadable file Date: Fri, 15 Jan 2021 13:34:23 +0200 Message-ID: <83zh1aa0xs.fsf@gnu.org> References: <86h7niwjl0.fsf@163.com> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="24229"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Zhu Zihao Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 15 12:35:20 2021 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 1l0NNv-0006Am-D9 for ged-emacs-devel@m.gmane-mx.org; Fri, 15 Jan 2021 12:35:19 +0100 Original-Received: from localhost ([::1]:43054 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l0NNu-00031U-D9 for ged-emacs-devel@m.gmane-mx.org; Fri, 15 Jan 2021 06:35:18 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:42890) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1l0NN5-0002WA-MH for emacs-devel@gnu.org; Fri, 15 Jan 2021 06:34:27 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:49200) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1l0NN5-00068b-Cy; Fri, 15 Jan 2021 06:34:27 -0500 Original-Received: from 84.94.185.95.cable.012.net.il ([84.94.185.95]:1891 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1l0NN4-0005D1-4f; Fri, 15 Jan 2021 06:34:26 -0500 In-Reply-To: <86h7niwjl0.fsf@163.com> (message from Zhu Zihao on Fri, 15 Jan 2021 19:00:43 +0800) 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:263072 Archived-At: > From: Zhu Zihao > Date: Fri, 15 Jan 2021 19:00:43 +0800 > > It's OK for me. But it's not an idiomatic way in distribution packaging. > For distrbution packaged Elisp packages, Lisp files usually placed at > /share/emacs/site-lisp. In FHS spec > (https://www.pathname.com/fhs/pub/fhs-2.3.html), /share should > only contains architecture-independant files, and obviously dynamic > library is not the case. They should be placed under /lib. > > My suggestion is add a new `native-load-path` Lisp variable and > `EMACSNATIVELOADPATH` environment variable to enable a dedicated search > path for native files. So you are saying that the Lisp part of a module should be installed under /usr/share/emacs/site-list, and it's shared-library part under /usr/lib? Wouldn't this complicate things? I'm not sure I understand the problem: doesn't a module normally come with a Lisp interface file? And if so, couldn't the module solve this inside the Lisp part, e.g., load the shared-library file explicitly? IOW, why do we need to treat this situation specially? Failing that, how about arranging for architecture-dependent subdirectories under site-lisp instead?