From: Drew Adams <drew.adams@oracle.com>
To: Jimmy Aguilar Mena <jimmy.aguilar@bsc.es>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : [ELPA] Package cleanup
Date: Tue, 29 Mar 2022 16:24:19 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488B8B8FC7A89ED8AB72598F31E9@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <20220329004337.nzeew6dlyqxm7wat@Ergus>
> It seems there are some packages there which haven't received any
> update in a very long time (>5 years). Maybe there is a way to
> put them is a sort of obsolete/archived/unmaintained state...
> In order to keep them, but at least not confuse the new users,
> or wrongly suggest to use them.
Some cars need to go to the mechanic every month,
which makes sense for them. Some don't. Some
people need to go to the doctor often; others
don't.
Why should Emacs assume that no change to a
package means the package is not being maintained
(let alone is obsolete)?
> I have found some packages that doesn't even work or rely on some
> features that were obsoleted or removed.
That's something entirely different. Report such
specific problems.
next prev parent reply other threads:[~2022-03-29 16:24 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 0:43 [ELPA] Package cleanup Jimmy Aguilar Mena
2022-03-29 16:24 ` Drew Adams [this message]
2022-03-29 21:41 ` [External] : " John Yates
2022-03-29 22:04 ` Drew Adams
2022-03-29 23:05 ` John Yates
2022-03-30 1:43 ` Drew Adams
2022-03-31 4:27 ` Richard Stallman
2022-03-30 7:31 ` Michael Albinus
2022-03-30 8:35 ` [External] : " Stefan Monnier
2022-03-30 14:09 ` Jimmy Aguilar Mena
2022-03-30 21:23 ` Stefan Monnier
2022-03-31 4:27 ` Richard Stallman
2022-03-30 3:12 ` Richard Stallman
2022-03-30 3:44 ` Po Lu
2022-03-30 7:56 ` João Távora
2022-03-30 4:56 ` Jimmy Aguilar Mena
2022-04-01 4:07 ` 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=SJ0PR10MB5488B8B8FC7A89ED8AB72598F31E9@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=jimmy.aguilar@bsc.es \
/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).