|
From: | Adam Porter |
Subject: | Re: [ELPA] New package: plz |
Date: | Mon, 9 May 2022 16:08:55 -0500 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.1 |
Hi Philip, On 5/9/22 14:50, Philip Kaludercic wrote:
Adam Porter <adam@alphapapa.net> writes:From d7ec5692547885f155007e7978d161aba3c3ad52 Mon Sep 17 00:00:00 2001 From: Adam Porter <adam@alphapapa.net> Date: Mon, 9 May 2022 11:17:02 -0500 Subject: [PATCH] * elpa-packages (plz): New package --- elpa-packages | 3 +++ 1 file changed, 3 insertions(+) diff --git a/elpa-packages b/elpa-packages index 51c17bc..65bb6a0 100644 --- a/elpa-packages +++ b/elpa-packages @@ -487,6 +487,9 @@ :auto-sync nil ) ("pinentry" :url "https://github.com/ueno/pinentry-el.git") + ("plz" :url "https://github.com/alphapapa/plz.el.git" + :doc "plz.info"How is plz.info generated? From what I see the content is the same as README.org, right? Unless something special is going on you should be able to let ELPA generate the file for you, instead of tracking the generated file in your repository.
It's generated the same way as the taxy.info file is for taxy, by the after-save-hook in the README.org file when I save it.
I'm not opposed to letting ELPA generate it for me, but I don't know if the output would be exactly the same. And despite my best efforts, I haven't been able to use the ELPA Makefiles to fetch and build packages locally (various errors about missing ".tmp.setdiff" files, directories that shouldn't exist but do, directories that should exist but don't, invalid git object names, invalid branches, forbidden git repos, unknown git options...it's hard to know where to begin debugging it), so I can't check its output myself.
[Prev in Thread] | Current Thread | [Next in Thread] |