all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefankangas@gmail.com>
To: rms@gnu.org
Cc: 59609@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#59609: 29.0.50; [PATCH] Better advertise (Non-)GNU ELPA in emacs manual
Date: Sat, 3 Dec 2022 16:00:41 -0800	[thread overview]
Message-ID: <CADwFkmkWX8fuTemPV2FxYQd4HVNOuiA5043pkk46Z=6u3muLmg@mail.gmail.com> (raw)
In-Reply-To: <E1p1c7K-00051h-Rk@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

>   > I see no risk that the packages will suddenly go away.  Under what
>   > circumstances would that happen?
>
> Here are two ways I can envision.
>
> If somehow the developers are no longer working on it in a way
> we can use.
>
> If it rots and needs substantial change and the developers
> are not interested in doing that.

I'm positive that these things can and will happen, but that's true also
for GNU ELPA and parts of Emacs itself (see lisp/obsolete/*.el).  Or
indeed with any software.  I'm not sure why this would need pointing out
specifically in the case of NonGNU ELPA.

Software dies at times.  C'est la vie.

>   >   But I don't see
>   > why we need to get into all that in this section, where we are just
>   > letting people know that GNU ELPA and NonGNU ELPA exist.
>
> It's about two lines -- not enough to qualify as "all that".

I was thinking more about the concept than the amount of text.  It
suggests that this concern is somehow specific to NonGNU ELPA.

FWIW, I believe the number of packages I've been using that have stopped
"being present" in my two decades or so with Emacs are... well, zero.
Zero packages.  Some are indeed unmaintained, but I still use them and
they work as well (or indeed badly) as they did ten or twenty years ago.





  reply	other threads:[~2022-12-04  0:00 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-26 13:44 bug#59609: 29.0.50; [PATCH] Better advertise (Non-)GNU ELPA in emacs manual Stefan Kangas
2022-11-26 14:20 ` Eli Zaretskii
2023-09-08 11:25   ` Stefan Kangas
2023-09-08 11:56     ` Eli Zaretskii
2023-09-08 15:04       ` Stefan Kangas
2023-09-11  0:40         ` Richard Stallman
2023-09-11  2:49           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 15:47       ` Drew Adams
2023-09-08 16:43       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-08 18:29         ` Eli Zaretskii
2023-09-08 18:47           ` Michael Albinus
2023-09-08 20:10           ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-11  0:40             ` Richard Stallman
2022-11-27 22:54 ` Richard Stallman
2022-11-30 23:54 ` Richard Stallman
2022-12-01  3:49   ` Stefan Kangas
2022-12-03 23:40     ` Richard Stallman
2022-12-04  0:00       ` Stefan Kangas [this message]
2022-12-14 22:20         ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CADwFkmkWX8fuTemPV2FxYQd4HVNOuiA5043pkk46Z=6u3muLmg@mail.gmail.com' \
    --to=stefankangas@gmail.com \
    --cc=59609@debbugs.gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.