From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: difference between elpa/README and Package Archive *info*
Date: Wed, 27 May 2020 09:53:31 -0700 [thread overview]
Message-ID: <86r1v5e2us.fsf@stephe-leake.org> (raw)
In-Reply-To: <87367ltq9f.fsf@rabkins.net> (Yoni Rabkin's message of "Wed, 27 May 2020 10:18:52 -0400")
Yoni Rabkin <yoni@rabkins.net> writes:
> The info node (elisp) Packaging > Package Archives, describes creating a
> tar file and a NAME-pkg.el file. It mentions https://elpa.gnu.org
> specifically.
>
> But the README file at (https://git.savannah.gnu.org/git/emacs/elpa.git)
> elpa/README states that elpa.gnu.org doesn't use tar files, nor do you
> need to create a NAME-pkg.el file.
>
> Is it that elpa.gnu.org is implemented differently? If so, the info file
> that references it should probably reflect how elpa.gnu.org actually
> works, how it differs from the "stock" setup, and why.
The info node describes what the code in package.el expects to see when
it accesses a url in package-archives..
The readme on ELPA describes what users of ELPA have to do.
In between are the build scripts on ELPA; they build the tar file and
NAME-pkg.el file from what the user provides.
Other archives may work differently, but they all present the same
interface to package.el.
--
-- Stephe
next prev parent reply other threads:[~2020-05-27 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-27 14:18 difference between elpa/README and Package Archive *info* Yoni Rabkin
2020-05-27 16:53 ` Stephen Leake [this message]
2020-05-27 17:40 ` Yoni Rabkin
2020-05-28 2:26 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86r1v5e2us.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).