unofficial mirror of bug-gnu-emacs@gnu.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: Wed, 30 Nov 2022 19:49:47 -0800	[thread overview]
Message-ID: <CADwFkmkiCnPLAURRMsaFt830LxGNhN4oSJe+28tjc=7sQP873w@mail.gmail.com> (raw)
In-Reply-To: <E1p0Wu6-0000em-KG@fencepost.gnu.org>

Richard Stallman <rms@gnu.org> writes:

>   > +  By default, Emacs downloads packages from GNU ELPA
>   > +(@url{https://elpa.gnu.org/}), a package archive maintained by the
>   > +Emacs developers and hosted by the GNU project.  It also downloads
>   > +packages from NonGNU ELPA (@url{https://elpa.nongnu.org/}).
>
>     I think it is ok to say this about NonGNU ELPA provided we say
>     clearly that these are packages we can't or should not include in
>     Emacs, so people should not depend on them to continue to be
>     present.

I see no risk that the packages will suddenly go away.  Under what
circumstances would that happen?

In some cases, we will delete packages from NonGNU ELPA, of course.
This is true for GNU ELPA also, and for Emacs itself.  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.





  reply	other threads:[~2022-12-01  3:49 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 [this message]
2022-12-03 23:40     ` Richard Stallman
2022-12-04  0:00       ` Stefan Kangas
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

  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='CADwFkmkiCnPLAURRMsaFt830LxGNhN4oSJe+28tjc=7sQP873w@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 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).