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: Path for system-wide .eln files Date: Sun, 30 Aug 2020 20:50:39 +0000 Message-ID: References: <83o8qocd32.fsf@gnu.org> <83blmndbpo.fsf@gnu.org> <838shrdb1c.fsf@gnu.org> <837dxbd93b.fsf@gnu.org> 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="39703"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.3 (gnu/linux) Cc: , Eli Zaretskii , Paul Eggert To: Ulrich Mueller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 30 22:51:36 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 1kCUIa-000AC5-MA for ged-emacs-devel@m.gmane-mx.org; Sun, 30 Aug 2020 22:51:36 +0200 Original-Received: from localhost ([::1]:42662 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kCUIZ-0008BP-MG for ged-emacs-devel@m.gmane-mx.org; Sun, 30 Aug 2020 16:51:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:48218) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kCUHx-0007kP-Hq for emacs-devel@gnu.org; Sun, 30 Aug 2020 16:50:57 -0400 Original-Received: from mx.sdf.org ([205.166.94.24]:64597) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kCUHv-0005Di-Cb; Sun, 30 Aug 2020 16:50:57 -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 07UKodst003813; Sun, 30 Aug 2020 20:50:39 GMT In-Reply-To: (Ulrich Mueller's message of "Sun, 30 Aug 2020 12:18:39 +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/08/30 16:33:54 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:254416 Archived-At: Ulrich Mueller writes: > Heading over from https://github.com/gentoo/gentoo/pull/16962 to here, > as suggested by Andrea: > > System-wide .eln files are currently installed in: > /usr/libexec/emacs/28.0.50/x86_64-pc-linux-gnu/eln-cache/ > > (I am using /usr here and in the following for better readability, > replace by ${exec_prefix} as appropriate.) > > I see two issues with this: > > - According to [1] the directory contains ".eln files compiled during > the build process." Therefore it is not a cache but a normal install > directory, and "eln-cache" is a misleading name. > (Or, from a wider perspective, a system-wide cache can never be in > /usr but should be in /var/cache. And it wouldn't be populated at > install time but at run time.) > > - The FHS [2] says that /usr/libexec is intended for "binaries run > by other programs". Do .eln files qualify as executable binaries? > IIUC they are loaded by dlopen, so they're pretty much libraries or > plugins which should go under /usr/lib{,64} instead. > > [1] https://akrl.sdf.org/gccemacs.html#org01229a9 > [2] https://refspecs.linuxfoundation.org/FHS_3.0/fhs/ch04s07.html Hi Ulrich, thanks for the interesting input. As for point 1 if this folder does not classify as cache because read only, should be easy to go for something more appropriate. Something as simple as "sys-eln" would work? (I'm not good with names sorry) For point 2: eln are opened with dlopen so they are technically shared libraries. They need to be loaded with some special treatment and cannot be used as simple shareds by C programs tho. To me this fits decently in the definition for /usr/libexec from your link: "includes internal binaries that are not intended to be executed directly by users or shell scripts. Applications may use a single subdirectory under /usr/libexec." But I understand they could fit in /usr/lib as well. Honestly I'm fine with one or the other :) Andrea