From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ulrich Mueller Newsgroups: gmane.emacs.devel Subject: Re: Path for system-wide .eln files Date: Sat, 05 Sep 2020 00:59:52 +0200 Message-ID: References: <83o8qocd32.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="33738"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) Cc: Andrea Corallo , Paul Eggert , "Andrea Corallo via Emacs development discussions." , Eli Zaretskii , Yuri Khan To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 05 01:00:43 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 1kEKhH-0008hp-9w for ged-emacs-devel@m.gmane-mx.org; Sat, 05 Sep 2020 01:00:43 +0200 Original-Received: from localhost ([::1]:57074 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kEKhG-0002I2-8l for ged-emacs-devel@m.gmane-mx.org; Fri, 04 Sep 2020 19:00:42 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:56764) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kEKgc-0001oN-GW for emacs-devel@gnu.org; Fri, 04 Sep 2020 19:00:02 -0400 Original-Received: from woodpecker.gentoo.org ([2001:470:ea4a:1:5054:ff:fec7:86e4]:43795 helo=smtp.gentoo.org) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kEKga-00035j-8S; Fri, 04 Sep 2020 19:00:01 -0400 In-Reply-To: (Stefan Monnier's message of "Fri, 04 Sep 2020 17:42:45 -0400") Received-SPF: pass client-ip=2001:470:ea4a:1:5054:ff:fec7:86e4; envelope-from=ulm@gentoo.org; helo=smtp.gentoo.org X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/04 18:59:58 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, RCVD_IN_DNSWL_NONE=-0.0001, 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:254534 Archived-At: >>>>> On Fri, 04 Sep 2020, Stefan Monnier wrote: >> The difference between the two directories is that the home directory >> may be shared between different architectures, while /usr/lib (or >> /usr/local/lib) is _not_ shared by its definition. Therefore the >> architecture makes sense in ~/.emacs.d/ but is redundant in /usr/lib/. > The extra info may be redundant but it does no harm. > The benefit is that /$DESTDIR/$libdir/emacs/native-lisp can be a normal > member of the "eln files search path", whereas otherwise it would have > to be treated specially. Would that really be a problem? The tradeoff is an ugly directory structure, in order to save a few lines of code. >> I'd very much prefer (also from a distro point of view) if the directory >> trees in /usr/share and /usr/lib would have a similar structure. That >> is, /usr/lib/emacs//..., and no arch triplet. > Other than aesthetic concerns, what is at stake? Is it completely excluded that additional types of files will be installed in /usr/lib/emacs/ in future? I believe it would make sense to establish a directory structure that can be generalised, instead of something that looks like an ad-hoc solution for one specific use case.