From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Akib Azmain Turja <akib@disroot.org>
Cc: Richard Stallman <rms@gnu.org>,
Philip Kaludercic <philipk@posteo.net>,
emacs-devel@gnu.org
Subject: Re: What to do about unmaintained ELPA packages
Date: Tue, 31 May 2022 08:33:13 -0400 [thread overview]
Message-ID: <jwvsfop6g18.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87a6ayt2mi.fsf@disroot.org> (Akib Azmain Turja's message of "Tue, 31 May 2022 16:31:17 +0600")
> Yeah, we can fix GNU ELPA packages, since those are part of Emacs.
> But what about NonGNU ELPA packages?
Actually, for the majority of packages, there is virtually no difference
between GNU and NonGNU in this respect: their official development takes
place elsewhere but we have our own branch in elpa.git/nongnu.git where
we can install any changes we may want.
And in both cases, installing changes on our own branch means that the
development has diverged ("forked"), which will spell pain in the future
if/when upstream's development continues.
IOW: we can do it, but there are strong motivations to refrain from
doing it.
Stefan
next prev parent reply other threads:[~2022-05-31 12:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-29 21:34 What to do about unmaintained ELPA packages Philip Kaludercic
2022-05-29 21:41 ` Stefan Monnier
2022-05-29 21:54 ` Dmitry Gutov
2022-05-29 23:08 ` Tim Cross
2022-05-30 11:14 ` Akib Azmain Turja
2022-05-30 6:58 ` Philip Kaludercic
2022-05-30 13:45 ` Lars Ingebrigtsen
2022-05-30 14:46 ` João Távora
2022-05-30 22:51 ` Ergus
2022-05-30 23:04 ` João Távora
2022-05-31 16:42 ` Philip Kaludercic
2022-05-31 22:08 ` João Távora
2022-06-01 5:57 ` Bozhidar Batsov
2022-06-01 22:56 ` Richard Stallman
2022-05-30 22:53 ` Richard Stallman
2022-05-31 10:31 ` Akib Azmain Turja
2022-05-31 12:33 ` Stefan Monnier [this message]
2022-05-31 13:39 ` Akib Azmain Turja
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=jwvsfop6g18.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=akib@disroot.org \
--cc=emacs-devel@gnu.org \
--cc=philipk@posteo.net \
--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).