From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Path for system-wide .eln files Date: Fri, 04 Sep 2020 22:58:55 -0400 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="10221"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Andrea Corallo , Paul Eggert , "Andrea Corallo via Emacs development discussions." , Eli Zaretskii , Yuri Khan To: Ulrich Mueller Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sat Sep 05 04:59:45 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 1kEOQa-0002Zo-Ex for ged-emacs-devel@m.gmane-mx.org; Sat, 05 Sep 2020 04:59:44 +0200 Original-Received: from localhost ([::1]:47348 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kEOQZ-0003U2-G8 for ged-emacs-devel@m.gmane-mx.org; Fri, 04 Sep 2020 22:59:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:54736) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kEOQ2-00034j-Gk for emacs-devel@gnu.org; Fri, 04 Sep 2020 22:59:10 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:51081) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kEOQ0-0007JF-2O; Fri, 04 Sep 2020 22:59:09 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 053EB805B8; Fri, 4 Sep 2020 22:59:06 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 42B3E80E06; Fri, 4 Sep 2020 22:58:57 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1599274737; bh=TQHFW7J3hcoSmbn6wV1XAb7y6MxqOuDBusI35Ejiymw=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=lgWWZUwXTXGbFrWMyMCi4YBq77sYwSPsF0JKaWpqCUapzILV6ztPwvJigrNtAaqf1 fwtkLpZphlGvDLMiHpieEI0FfQUybEy6d/h5nuAnIRTk0b8zfYWoqxTdmMW+QSOCmz 1iMWEwbQ21D+7IN9b1/+JznBJplM2/7LidvA+wLiK46oPMzEDBCHYZT1k6u8aXq5tJ MhSgmeKgUQia7ZgS5H6hTNxNKQy+5QOlpucBhFgGUzACtQ42R8GzUG1KaU6uzogbL0 Qzk5euaF6uQC1k0Hk2MOHhHi7eyTGUZlU5WtKaiUnvnpZB8ubuJcpJpVzqhY+jXgmI U08v5JSdDQ4EQ== Original-Received: from alfajor (unknown [45.72.232.131]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id EDACD120737; Fri, 4 Sep 2020 22:58:56 -0400 (EDT) In-Reply-To: (Ulrich Mueller's message of "Sat, 05 Sep 2020 00:59:52 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/04 22:59:06 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=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:254535 Archived-At: >> 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? Beside the unneeded extra complexity, it would also make it either impossible to change the order between the files in the one-and-only-system-dir and the-other-dirs, or would require yet more complexity to provide extra flexibility. So, yes, I think it would really be a problem. >> 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? No, but I can't think of any reason why that would be more likely to collide with `native-files` than with `26.3`. If you're still worried, we can go back to $DESTDIR/$libdir/emacs/$VERSION/native-lisp where the $VERSION is redundant. I wouldn't be bothered by this redundancy. Stefan