From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Andrew Goh <andrewgoh95@yahoo.com.sg>
Cc: 63536@debbugs.gnu.org
Subject: bug#63536: Feature Request
Date: Wed, 17 May 2023 09:53:38 -0700 [thread overview]
Message-ID: <c057f731-bceb-3f91-c56d-875ffd3b5b0b@gmail.com> (raw)
In-Reply-To: <83bkijxenf.fsf@gnu.org>
On 5/17/2023 6:37 AM, Eli Zaretskii wrote:
> So you want a command to check whether a newer Emacs is available?
> But where should this command look? Many (most?) people install
> precompiled binaries prepared by their distros, and I assume those
> distros have their "check for updates" service or something?
>
> We could check on the GNU FTP site, but how many users will want to
> download and build Emacs from sources?
>
> What do other people think about this?
I think we could fairly easily *check* for the existence of a newer
Emacs release, but the hard part is what to do about it. Is it enough to
merely tell the user, "Emacs 29.1 is released," and just expect the user
to figure out how to update?
For users who get their Emacs from their distro, the distro is
responsible for updates then. We can ignore that case.[1] (Ditto for any
other package manager: PPAs, Homebrew, etc.)
However, for users who get their Emacs from GNU FTP, the only update
mechanism right now is 100% manual. It would be interesting to try to
fix that, but it also seems difficult: if the user downloaded Emacs and
compiled from source, can we make 100% sure that we can do that
programmatically for the next release? What if Emacs adds a new library
dependency? Maybe GNU FTP could also distribute binaries in some fashion
instead[2], but that's yet another complexity to work out. If we
distributed binaries, how would we do so?
If someone wanted to spend the time to figure out all the issues with
this, I think there'd be value in it, but I also think it's more effort
than it's worth (unless this is literally just a notification, nothing
more).
[1] That's what Firefox does too: if you install Firefox from Mozilla,
it'll handle updating itself, but if you install it from your distro,
the distro handles the updates.
[2] There are the MS-Windows binaries, but I don't think we should be
spending too much effort on something that would only benefit users of a
nonfree OS.
next prev parent reply other threads:[~2023-05-17 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1553770628.2069339.1684237196253.ref@mail.yahoo.com>
2023-05-16 11:39 ` bug#63536: Feature Request Andrew Goh via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-16 15:46 ` Eli Zaretskii
[not found] ` <2050007547.2204916.1684290974957@mail.yahoo.com>
2023-05-17 10:58 ` Eli Zaretskii
[not found] ` <1884442844.2472195.1684329429592@mail.yahoo.com>
2023-05-17 13:37 ` Eli Zaretskii
2023-05-17 16:53 ` Jim Porter [this message]
2023-05-19 13:36 ` Benjamin Riefenstahl
2023-05-17 14:04 ` Payas Relekar
2023-05-17 17:16 ` Eli Zaretskii
2023-05-17 15:40 ` Payas Relekar
2023-05-17 15:51 ` Payas Relekar
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=c057f731-bceb-3f91-c56d-875ffd3b5b0b@gmail.com \
--to=jporterbugs@gmail.com \
--cc=63536@debbugs.gnu.org \
--cc=andrewgoh95@yahoo.com.sg \
--cc=eliz@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).