From: Stephen Leake <stephen_leake@stephe-leake.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: daniele@grinta.net, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: decision on moving core packages to ELPA; also move to obsolete?
Date: Wed, 16 Dec 2020 11:21:31 -0800 [thread overview]
Message-ID: <86bletmu9w.fsf@stephe-leake.org> (raw)
In-Reply-To: <83o8iuann7.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 15 Dec 2020 21:13:16 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Stephen Leake <stephen_leake@stephe-leake.org>
>> Cc: daniele@grinta.net, Stefan Monnier <monnier@iro.umontreal.ca>,
>> emacs-devel@gnu.org
>> Date: Tue, 15 Dec 2020 10:53:38 -0800
>>
>> >> > If so, what happens with installed Lisp files under /usr/share/ ?
>> >
>> > They stay there, but ~/.emacs.d/elpa is earlier in load-path.
>>
>> And also, once bundling ELPA packages in the tarball works, the package
>> can be removed from Emacs core, simplifying the pakcage maintenance
>> process.
>
> So please describe how you envision the process of building a release
> tarball under this assumption. E.g., how do I know which version of
> package A I want to bundle is stable enough to go to a bugfix elease
> of Emacs?
The simplest choice is the ELPA version that is current at the time the
tarball is built.
Nominally, ELPA versions are defined to be stable. But given the ease of
releasing a new version via ELPA, some package developers may have a
policy of releasing without significant testing. In that case, it might
make sense to ask developers to put more effort into validating a
particular version for a release. Or simply say such a package is not a
good candidate for bundling.
In my case, I always run a large test suite on ada-mode before I do an
ELPA release.
If we want to freeze some earlier version at the start of release
testing (as opposed to final tarball build time), we'd need some
mechanism to record the versions of all the bundled packages, and then
only use those versions in testing. And a way to change that frozen
version number for a bug fix.
Or ask ELPA packages that are bundled to also freeze for the duration of
release testing; that would be reasonable, and simplify handling package
bug fixes.
--
-- Stephe
next prev parent reply other threads:[~2020-12-16 19:21 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 19:59 decision on moving core packages to ELPA; also move to obsolete? Stephen Leake
2020-12-14 20:07 ` Eli Zaretskii
2020-12-14 23:40 ` Stefan Monnier
2020-12-15 5:06 ` Eli Zaretskii
2020-12-15 9:32 ` Daniele Nicolodi
2020-12-15 16:57 ` Eli Zaretskii
2020-12-15 17:03 ` Stefan Monnier
2020-12-15 17:30 ` Glenn Morris
2020-12-15 17:43 ` Glenn Morris
2020-12-15 17:54 ` Glenn Morris
2020-12-15 19:50 ` Stefan Monnier
2020-12-15 18:28 ` Eli Zaretskii
2020-12-15 18:49 ` Stephen Leake
2020-12-15 18:53 ` Stephen Leake
2020-12-15 19:13 ` Eli Zaretskii
2020-12-15 19:54 ` Stefan Monnier
2020-12-15 20:11 ` Eli Zaretskii
2020-12-15 20:55 ` Dmitry Gutov
2020-12-16 15:33 ` Eli Zaretskii
2020-12-16 16:09 ` Dmitry Gutov
2020-12-15 22:01 ` Stefan Monnier
2020-12-16 3:13 ` Tests in core depending on GNU ELPA packages (was: decision on moving core packages to ELPA; also move to obsolete?) Thomas Fitzsimmons
2020-12-16 3:24 ` Tests in core depending on GNU ELPA packages Stefan Monnier
2021-02-19 1:09 ` Thomas Fitzsimmons
2021-02-19 1:15 ` Stefan Monnier
2020-12-16 17:53 ` decision on moving core packages to ELPA; also move to obsolete? Eli Zaretskii
2020-12-16 18:35 ` Stefan Monnier
2020-12-16 19:23 ` Eli Zaretskii
2020-12-16 20:01 ` Stefan Monnier
2020-12-16 20:05 ` Eli Zaretskii
2020-12-16 20:13 ` Stefan Monnier
2020-12-16 19:46 ` Stephen Leake
2020-12-16 20:10 ` Stefan Monnier
2020-12-16 19:21 ` Stephen Leake [this message]
2020-12-16 19:56 ` Eli Zaretskii
2020-12-15 19:57 ` Stefan Monnier
2020-12-15 20:16 ` Eli Zaretskii
2020-12-15 22:09 ` Stefan Monnier
2020-12-16 8:29 ` Michael Albinus
2020-12-16 14:20 ` Stefan Monnier
2020-12-16 14:42 ` Michael Albinus
2020-12-16 8:47 ` Andrea Corallo via Emacs development discussions.
2020-12-16 17:56 ` Eli Zaretskii
2020-12-16 18:46 ` Stefan Monnier
2020-12-16 19:28 ` Eli Zaretskii
2020-12-16 20:05 ` Stefan Monnier
2020-12-15 18:33 ` Eli Zaretskii
2020-12-15 20:11 ` Stefan Monnier
2020-12-15 20:29 ` Eli Zaretskii
2020-12-15 22:25 ` Stefan Monnier
2020-12-16 17:59 ` Eli Zaretskii
2020-12-16 18:50 ` Stefan Monnier
2020-12-16 19:32 ` Eli Zaretskii
2020-12-16 20:06 ` Stefan Monnier
2020-12-16 20:19 ` Eli Zaretskii
2020-12-16 21:03 ` Stefan Monnier
2020-12-16 19:44 ` Stephen Leake
2020-12-16 20:01 ` Eli Zaretskii
2021-01-10 23:05 ` ELPA notes, README Stephen Leake
2021-01-10 23:14 ` Stefan Monnier
2020-12-15 14:05 ` decision on moving core packages to ELPA; also move to obsolete? Stefan Monnier
2020-12-15 17:04 ` Eli Zaretskii
2020-12-15 17:28 ` Stefan Monnier
2020-12-15 5:46 ` Lars Ingebrigtsen
2020-12-15 18:50 ` Stephen Leake
2021-01-07 17:33 ` Stephen Leake
2021-01-07 20:00 ` Stefan Monnier
2021-01-08 17:00 ` Stephen Leake
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=86bletmu9w.fsf@stephe-leake.org \
--to=stephen_leake@stephe-leake.org \
--cc=daniele@grinta.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).