From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Philip Kaludercic Newsgroups: gmane.emacs.devel Subject: Re: Easy configuration of a site-lisp directory Date: Sun, 08 Aug 2021 18:53:11 +0000 Message-ID: <87tujzkbu0.fsf@posteo.net> References: <87y29cj65y.fsf@posteo.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="25826"; mail-complaints-to="usenet@ciao.gmane.io" Cc: emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Sun Aug 08 20:53:53 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 1mCnvk-0006V6-AY for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Aug 2021 20:53:52 +0200 Original-Received: from localhost ([::1]:47454 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mCnvi-0001Tn-NL for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Aug 2021 14:53:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58578) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mCnvB-0000mj-Qy for emacs-devel@gnu.org; Sun, 08 Aug 2021 14:53:18 -0400 Original-Received: from mout02.posteo.de ([185.67.36.66]:39547) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mCnv9-0003WV-N2 for emacs-devel@gnu.org; Sun, 08 Aug 2021 14:53:17 -0400 Original-Received: from submission (posteo.de [89.146.220.130]) by mout02.posteo.de (Postfix) with ESMTPS id 455F3240104 for ; Sun, 8 Aug 2021 20:53:13 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1628448793; bh=bUtaC6x2/KvUV59baez6mdO+GydjD7LNB/r1zh3XA2Y=; h=From:To:Cc:Subject:Date:From; b=r19xgjE4TKblzM9cW7Nb5j1ga0EHpt8cdIs3KQtIovGnEnGMLEhM8wayYcAvqh6UB oKh3+qOiiPWxZV6VaC5N7Al157Z3C2lAZGlpaR7U0d7UVsLal2lmHX4gX3EkwmT9y+ JmcRWUum1E91+SQwGShSX2quV3usJnmC77ZE5+3DK2mb4eLRdhKQYs7xuNBeISLT/y iFEkzSf2FRezaA/TvzV00ke5TSWEXbDKo0UXXzfklzYhwmU26Omhi7W5SjOwiny9py DNtKP5NO5l1kVxaM8TB2lM4wTmoIp6XGrWz86ODW0T0NYoXMUTU+vbz0+KQBlxvaxO LDfNYZ8i5d6MA== Original-Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4GjSyw49lcz9rxR; Sun, 8 Aug 2021 20:53:12 +0200 (CEST) In-Reply-To: (Stefan Monnier's message of "Sun, 08 Aug 2021 14:18:59 -0400") Received-SPF: pass client-ip=185.67.36.66; envelope-from=philipk@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -27 X-Spam_score: -2.8 X-Spam_bar: -- X-Spam_report: (-2.8 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, 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:272209 Archived-At: Stefan Monnier writes: > Philip Kaludercic [2021-08-08 15:40:57] wrote: >> I have been using something along these lines for a while now, and >> wanted to suggest adding this to Emacs/ELPA: > [...] >> The fundamental idea is to have an easy-to-use ~/.emacs.d/site-lisp/ >> directory where a user can clone any repository or create their own, >> without having to manually add these to load-path, generate autoloads or >> byte compile. > > FWIW, I use `elpa-admin.el` for that. > The advantage being that the package.el is made aware of them. What is the advantage in making package.el aware? > Admittedly, `elpa-admin.el` doesn't provide that "out of the box", but > I'd welcome changes to improve this use case. It go become an > alternative to `straight.el`. On the topic of package.el, a more general idea I had was to make package.el more generic, with different backends. Then you could have one backend for elpa packages, one for local "packages", etc. But that would certainly take more effort to design and implement that what I have suggested here. > > Stefan > > > -- Philip Kaludercic