From: Eli Zaretskii <eliz@gnu.org>
To: JD Smith <jdtsmith@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Moving packages out of core to ELPA
Date: Sat, 17 Feb 2024 17:51:24 +0200 [thread overview]
Message-ID: <86jzn3t7gj.fsf@gnu.org> (raw)
In-Reply-To: <E1FC4CF1-F342-4167-A007-C5BD2DFCE56C@gmail.com> (message from JD Smith on Sat, 17 Feb 2024 09:40:19 -0500)
> From: JD Smith <jdtsmith@gmail.com>
> Date: Sat, 17 Feb 2024 09:40:19 -0500
>
> There was a recent discussion about which lisp/progmodes packages belong in core. A sentiment was
> expressed that useful languages with non-negligible user bases should probably go in, and others should be
> in ELPA.
>
> I want to bring up a related point: it should be possible to retire packages from core, once their relevance
> drops below a critical threshold [1].
We usually first retire such packages to lisp/obsolete/. There, they
are still available, but need to be loaded manually. Moving something
directly to ELPA might be too drastic, assuming someone somewhere
still want to use it.
next prev parent reply other threads:[~2024-02-17 15:51 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-17 14:40 Moving packages out of core to ELPA JD Smith
2024-02-17 15:51 ` Eli Zaretskii [this message]
2024-02-17 16:22 ` JD Smith
2024-02-17 16:51 ` Eli Zaretskii
2024-02-17 17:08 ` JD Smith
2024-02-17 17:29 ` Eli Zaretskii
2024-02-17 18:52 ` JD Smith
2024-02-17 19:20 ` Eli Zaretskii
2024-02-17 20:56 ` [External] : " Drew Adams
2024-02-17 21:16 ` JD Smith
2024-02-18 6:28 ` Eli Zaretskii
2024-02-18 12:57 ` JD Smith
2024-02-18 13:46 ` Po Lu
2024-02-18 14:03 ` JD Smith
2024-02-18 14:08 ` Po Lu
2024-02-18 14:17 ` JD Smith
2024-02-18 14:17 ` Eli Zaretskii
2024-02-18 14:19 ` JD Smith
2024-02-18 14:22 ` Po Lu
2024-02-17 17:42 ` [External] : " Drew Adams
2024-02-17 18:21 ` JD Smith
2024-02-17 18:32 ` Eli Zaretskii
2024-02-17 19:01 ` JD Smith
2024-02-17 20:50 ` Drew Adams
2024-02-18 1:55 ` Po Lu
2024-02-18 2:27 ` JD Smith
2024-02-18 3:47 ` Po Lu
2024-02-18 1:42 ` Po Lu
2024-02-18 2:14 ` JD Smith
2024-02-18 3:39 ` Po Lu
2024-02-18 7:25 ` Po Lu
2024-02-18 12:39 ` JD Smith
2024-02-18 13:08 ` Eli Zaretskii
2024-02-18 13:15 ` Po Lu
2024-02-18 7:14 ` Eli Zaretskii
2024-02-18 12:19 ` Dmitry Gutov
2024-02-18 13:06 ` Eli Zaretskii
2024-02-18 13:27 ` JD Smith
2024-02-18 13:06 ` Po Lu
2024-02-18 13:13 ` Dmitry Gutov
2024-02-18 13:51 ` Po Lu
2024-02-18 14:19 ` Dmitry Gutov
2024-02-18 14:26 ` Po Lu
2024-02-18 14:38 ` Dmitry Gutov
2024-02-19 18:09 ` Stefan Kangas
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=86jzn3t7gj.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=jdtsmith@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).