GNU bug report logs - #63536
Function to update Emacs itself (for example 29.1 to 29.2)

Previous Next

Package: emacs;

Reported by: Andrew Goh <andrewgoh95 <at> yahoo.com.sg>

Date: Tue, 16 May 2023 11:41:01 UTC

Severity: wishlist

Tags: wontfix

Done: Stefan Kangas <stefankangas <at> gmail.com>

Bug is archived. No further changes may be made.

Full log


Message #29 received at 63536 <at> debbugs.gnu.org (full text, mbox):

From: Payas Relekar <relekarpayas <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 63536 <at> debbugs.gnu.org, andrewgoh95 <at> yahoo.com.sg
Subject: Re: bug#63536: Feature Request
Date: Wed, 17 May 2023 21:21:48 +0530
Eli Zaretskii <eliz <at> gnu.org> writes:

>> From: Payas Relekar <relekarpayas <at> gmail.com>
>> Cc: Andrew Goh <andrewgoh95 <at> yahoo.com.sg>,  63536 <at> debbugs.gnu.org
>> Date: Wed, 17 May 2023 19:34:06 +0530
>>
>> The idea itself is valid, as long as the update check happens only at
>> explicit user action. The command should only compare current version of
>> Emacs with the latest update and inform user about the difference. Then
>> the onus is on user to proceed with the update. Command output can point
>> them to relevant section of the manual, informing of ways to install
>> (and also update) Emacs.
>
> How will we know where to look?  That's the main technical issue with
> this, I think.
>

Sorry, I missed this in previous mail. Where do we look? GNU Emacs
stable release URL, of course. As long as the latest version available
upstream (FTP or the git branch directly) is higher than user's version,
we are good to report.

If the users see their package manager does not have the latest version,
that's a good motivation for reporting it there. But the wording should
be clear for the same.

--




This bug report was last modified 179 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.