From: Stephen Leake <stephen_leake@stephe-leake.org>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: access to ELPA development packages?
Date: Thu, 22 Jul 2021 06:17:00 -0700 [thread overview]
Message-ID: <864kcm4hf7.fsf@stephe-leake.org> (raw)
In-Reply-To: <868s1z42nz.fsf@stephe-leake.org> (Stephen Leake's message of "Wed, 21 Jul 2021 17:23:28 -0700")
Stephen Leake <stephen_leake@stephe-leake.org> writes:
> When non-gnu ELPA was introduced, I believe Stefan also made available
> devel/alpha versions of the gnu and non-gnu packages; the ELPA server
> packages the current head in each package, rather than the last version
> change.
>
> However, I can't find any docs on how to access that; I looked in the
> Gnu ELPA README, and searched this mailing list archive (never a satisfying
> experience).
This part I figured out:
(add-to-list 'package-archives (cons "gnu-devel" "https://elpa.gnu.org/devel"))
> Can we put instructions for accessing it on
> the ELPA home webpage, or in elpa/admin/README? I'm not clear how to
> edit the ELPA home webpage.
I think we should do this.
--
-- Stephe
next prev parent reply other threads:[~2021-07-22 13:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-22 0:23 access to ELPA development packages? Stephen Leake
2021-07-22 13:17 ` Stephen Leake [this message]
2021-07-23 6:26 ` Bozhidar Batsov
2021-07-23 11:04 ` Philip Kaludercic
2021-07-23 11:42 ` Dmitry Gutov
2021-07-26 0:16 ` Richard Stallman
2021-07-26 20:52 ` Philip Kaludercic
2021-07-26 22:01 ` dick
2021-07-27 8:12 ` Philip Kaludercic
2021-07-27 5:53 ` Stephen Leake
2021-07-23 15:14 ` Stefan Monnier
2021-07-26 20:34 ` Yuan Fu
2021-08-03 22:17 ` Stefan Monnier
2021-07-31 7:08 ` Stephen Leake
2021-07-31 11:21 ` Basil L. Contovounesios
2021-08-01 7:49 ` Richard Stallman
2021-08-02 1:06 ` Richard Stallman
2021-07-28 1:01 ` Richard Stallman
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=864kcm4hf7.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).