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: Easy configuration of a site-lisp directory Date: Sun, 08 Aug 2021 19:16:54 -0400 Message-ID: References: <87y29cj65y.fsf@posteo.net> <87czqna77n.fsf@dick> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="38816"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: Philip Kaludercic , emacs-devel@gnu.org To: dick Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Mon Aug 09 01:17:37 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 1mCs2y-0009pL-NK for ged-emacs-devel@m.gmane-mx.org; Mon, 09 Aug 2021 01:17:36 +0200 Original-Received: from localhost ([::1]:33826 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mCs2x-00020g-B5 for ged-emacs-devel@m.gmane-mx.org; Sun, 08 Aug 2021 19:17:35 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:55288) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mCs2R-0001Lw-Se for emacs-devel@gnu.org; Sun, 08 Aug 2021 19:17:03 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:16916) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mCs2N-0002Ke-3j for emacs-devel@gnu.org; Sun, 08 Aug 2021 19:17:02 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 40B434408BB; Sun, 8 Aug 2021 19:16:57 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id C2F924407D1; Sun, 8 Aug 2021 19:16:55 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1628464615; bh=YGj9igfhYG/5N7ztrvHubxa2jAhB0Xvfmrj6XW/x+e8=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=BzU31iw2wbHIQg9q9/wfqCCfV7KtIe+GmX0RAq0F9dnEWqZGkSrD0bxgaNYa5O40q KN2ZE5lxITNvv1Qx1l1+MR3RI6zWfZAHPnsRdc9iSMNeVRoFVnB34/UAIx1nqbEu8o cjuXGTorO2w8+PeKwfsVIu5V1VYScMJqL4DLNSVq9BEgHtk6efAAdFAf4OtgpMYPet LEy6qsyJeqqMf+wIwP3uWHsAynrGh+j1FoHACgQM5IZtE9bg7WxeQqgz09GfbLJVB7 HjMFqQWa+oP3aI1akVdttW+IyP6rLqminv5YV7JOLdr5xR5paE7luLfm59NDlwoS+w KRRljM4FZ5vSw== Original-Received: from alfajor (unknown [216.154.29.138]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 96A87120304; Sun, 8 Aug 2021 19:16:55 -0400 (EDT) In-Reply-To: <87czqna77n.fsf@dick> (dick's message of "Sun, 08 Aug 2021 18:43:08 -0400") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca 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:272214 Archived-At: > SM> Admittedly, `elpa-admin.el` doesn't provide that "out of the box", but I'd > SM> welcome changes to improve this use case. It go become an alternative to > SM> `straight.el`. > I was hoping ELPASO (https://github.com/dickmao/elpaso) would be the > elpa-admin-aware alternative to straight. I do appreciate that "not invented here" > is reason enough not to look into someone else's project. I wasn't aware (or forgot about) that one. AFAICT it generates a tarball from a remote Git repository and then installs it "normally", right? I think Philip intends instead to have the local Git clone *be* the installed package (which is also how I use elpa-admin.el). Basically, the way I do it is to setup a local nongnu.git clone with something like `git clone ../nongnu.git; cd nongnu; make`. Then add this local `.../nongnu` to your `package-directory-list`. This is done once and for all. Once that is done, installing a new package amounts to: - edit `nongnu/elpa-packages` to add the package's spec - `cd .../nongnu; make packages/PKG>; make packages/PKG>` - That's it [ The second `make` is because the first only fetches the package and crates the worktree, while the second then builds the -pkg.el and -autoloads.el and compiles the files. ] Packages can be updated with: - `cd .../nongnu; make worktrees; make`. But as it stands, this comes with its fair share of rough edges, some of which are plain bugs in `elpa-admin.el`, others are simply missing features. The main advantage for me is that things like `C-h f` bring me straight to the Git-managed source code. Stefan