From: Jeremy Bryant <jb@jeremybryant.net>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
emacs-devel@gnu.org, monnier@iro.umontreal.ca,
philipk@posteo.net
Subject: Candidate packages for ELPA bundling [Was: Re: Why not include all ELPA packages in an Emacs release?]
Date: Fri, 07 Jun 2024 22:55:36 +0100 [thread overview]
Message-ID: <87wmn076zr.fsf@jeremybryant.net> (raw)
In-Reply-To: <CADwFkmk-=b6h4=jC+ZyPx=DXSUz9nxoCvhDRWpdL9CiQNd-nSg@mail.gmail.com> (Stefan Kangas's message of "Wed, 29 May 2024 13:44:37 -0700")
Stefan Kangas <stefankangas@gmail.com> writes:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> What we discussed was the desire to move packages out of core in a way
>> that a release tarball would include those package. That is what we
>> have a consensus about (but not a complete and satisfactory solution
>> yet).
>
> It's possible that we have interpreted the previous discussions a bit
> differently, or that I'm filling in too many blanks.
>
> My understanding was that this was always going to be something like
> 1) make it possible to ship ELPA packages with core Emacs and then
> 2) decide which packages should be included.
>
> To my mind, step 2 could either be restricted to only include packages
> that used to be in core, or it could not be. The difference is not very
> big, at least not in principle, since before we bundle even two
> packages, we still have to solve the issue of how to bundle even one.
>
>> Back to the suggestion in this thread: I cannot really see why would
>> we want to add almost 500 packages to Emacs. Especially since AFAIR
>> some of them solve the same or very similar problems in different,
>> sometimes even contradictory, ways.
Now, understood.
>>
>> If there are packages on ELPA which we consider to be a must for users
>> (I don't think there are, but maybe I'm forgetting something), lets
>> add them to core instead.
>
> Not sure if there are any that are a must, but I do think a few of them
> would be good to have included. For example, `json-mode` would be nice
> to have available OOTB (though we now have `json-ts-mode` too).
Proposal:
How about selecting 1 package to work on bundling by ease of
implementation.
For example, Philip's auto-header package is on ELPA, and Philip has
ELPA knowledge. Philip, WDYT?
(Reviewing the feature branches they are constructed in terms of general
examples, it may help to have a concrete single package to work on bundling?)
next prev parent reply other threads:[~2024-06-07 21:55 UTC|newest]
Thread overview: 69+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-28 8:48 Why not include all ELPA packages in an Emacs release? Jeremy Bryant
2024-05-28 23:15 ` Stefan Kangas
2024-05-28 23:56 ` Stefan Monnier
2024-05-29 5:59 ` Philip Kaludercic
2024-05-29 11:44 ` Eli Zaretskii
2024-05-29 15:27 ` Arash Esbati
2024-05-29 15:40 ` Eli Zaretskii
2024-05-29 16:06 ` Philip Kaludercic
2024-05-29 19:33 ` Andrea Corallo
2024-05-30 19:25 ` Adding AUCTeX to core " Jeremy Bryant
2024-05-30 19:33 ` Philip Kaludercic
2024-05-31 18:58 ` Jeremy Bryant
2024-06-07 22:00 ` Jeremy Bryant
2024-06-08 6:56 ` Philip Kaludercic
2024-06-08 9:40 ` Arash Esbati
2024-06-08 15:25 ` Stefan Monnier
2024-06-08 15:49 ` Po Lu
2024-06-09 3:54 ` Stefan Monnier
2024-06-09 19:39 ` Stefan Kangas
2024-05-29 22:16 ` Arash Esbati
2024-05-29 22:19 ` Dmitry Gutov
2024-05-30 6:25 ` Philip Kaludercic
2024-05-30 6:33 ` Daniel Mendler via Emacs development discussions.
2024-05-30 7:28 ` Philip Kaludercic
2024-05-30 8:15 ` Daniel Mendler via Emacs development discussions.
2024-05-30 15:20 ` Philip Kaludercic
2024-05-29 20:35 ` Tassilo Horn
2024-05-29 22:04 ` Arash Esbati
2024-05-30 5:51 ` Eli Zaretskii
2024-05-30 10:52 ` Arash Esbati
2024-05-30 5:49 ` Eli Zaretskii
2024-05-30 7:55 ` Po Lu
2024-05-30 11:20 ` Eli Zaretskii
2024-05-30 11:53 ` Po Lu
2024-05-30 12:19 ` Eli Zaretskii
2024-05-30 12:58 ` Po Lu
2024-05-30 14:11 ` Stefan Monnier
2024-05-30 14:26 ` Po Lu
2024-05-30 13:53 ` Stefan Monnier
2024-05-30 14:05 ` Po Lu
2024-05-30 15:02 ` Stefan Monnier
2024-05-30 8:00 ` Philip Kaludercic
2024-05-29 20:44 ` Stefan Kangas
2024-05-30 5:09 ` Eli Zaretskii
2024-06-07 21:48 ` Moving core packages to ELPA [Was: Re: Why not include all ELPA packages in an Emacs release?] Jeremy Bryant
2024-06-08 6:14 ` Eli Zaretskii
2024-06-08 8:10 ` Michael Albinus
2024-06-08 8:38 ` Eli Zaretskii
2024-06-08 15:55 ` Michael Albinus
2024-06-08 16:47 ` Eli Zaretskii
2024-06-08 16:59 ` Michael Albinus
2024-06-07 21:55 ` Jeremy Bryant [this message]
2024-06-08 1:44 ` Candidate packages for ELPA bundling " Po Lu
2024-06-08 2:11 ` Dmitry Gutov
2024-06-08 2:46 ` Po Lu
2024-06-08 6:41 ` Philip Kaludercic
2024-06-08 6:54 ` Po Lu
2024-06-08 7:47 ` Philip Kaludercic
2024-06-08 15:06 ` Stefan Monnier
2024-06-08 16:24 ` Philip Kaludercic
2024-06-08 15:09 ` Stefan Monnier
2024-06-08 6:25 ` Eli Zaretskii
2024-06-08 6:48 ` Po Lu
2024-06-08 15:18 ` Stefan Monnier
2024-06-08 15:37 ` Po Lu
2024-06-08 15:53 ` Stefan Monnier
2024-06-09 0:06 ` Po Lu
2024-06-09 3:55 ` Stefan Monnier
2024-06-08 6:55 ` Philip Kaludercic
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=87wmn076zr.fsf@jeremybryant.net \
--to=jb@jeremybryant.net \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=philipk@posteo.net \
--cc=stefankangas@gmail.com \
/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).