From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Jim Porter Newsgroups: gmane.emacs.bugs Subject: bug#63536: Feature Request Date: Wed, 17 May 2023 09:53:38 -0700 Message-ID: References: <1553770628.2069339.1684237196253.ref@mail.yahoo.com> <1553770628.2069339.1684237196253@mail.yahoo.com> <83sfbwz3cp.fsf@gnu.org> <2050007547.2204916.1684290974957@mail.yahoo.com> <83y1lnxlzo.fsf@gnu.org> <1884442844.2472195.1684329429592@mail.yahoo.com> <83bkijxenf.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29654"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 63536@debbugs.gnu.org To: Eli Zaretskii , Andrew Goh Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed May 17 18:54:23 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pzKPu-0007Tj-6p for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 17 May 2023 18:54:22 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pzKPl-0005PC-Pr; Wed, 17 May 2023 12:54:13 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pzKPf-00059S-L0 for bug-gnu-emacs@gnu.org; Wed, 17 May 2023 12:54:08 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1pzKPa-0001wL-JN for bug-gnu-emacs@gnu.org; Wed, 17 May 2023 12:54:07 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pzKPa-0001Xy-Ax for bug-gnu-emacs@gnu.org; Wed, 17 May 2023 12:54:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Jim Porter Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 17 May 2023 16:54:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 63536 X-GNU-PR-Package: emacs Original-Received: via spool by 63536-submit@debbugs.gnu.org id=B63536.16843424265917 (code B ref 63536); Wed, 17 May 2023 16:54:02 +0000 Original-Received: (at 63536) by debbugs.gnu.org; 17 May 2023 16:53:46 +0000 Original-Received: from localhost ([127.0.0.1]:50811 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pzKPJ-0001XM-V8 for submit@debbugs.gnu.org; Wed, 17 May 2023 12:53:46 -0400 Original-Received: from mail-pl1-f181.google.com ([209.85.214.181]:58867) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pzKPI-0001X4-97 for 63536@debbugs.gnu.org; Wed, 17 May 2023 12:53:44 -0400 Original-Received: by mail-pl1-f181.google.com with SMTP id d9443c01a7336-1ae3f6e5d70so10633475ad.1 for <63536@debbugs.gnu.org>; Wed, 17 May 2023 09:53:44 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684342418; x=1686934418; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:mime-version:date:message-id:from:to:cc :subject:date:message-id:reply-to; bh=tjPxfbv5LVG91A9E+cywnl5RYdep2vWpj93tE4eNZR8=; b=GxQlradWX8XQZmXEaGuRWMBhIszGf7p6QNpgS2H6K4Yy65Tj/Vx8eO44gAG3MsSAIM J+uXyzkwQeYBo+JU70t5cLMQ5qEpvqVXeVCNM7EUv3rM8+ELIIn8B2KYef0DmR53WfLR n0B83ZiVJLlpGHaKHO9I2a8XIOIPQK/gompBgV1glf1C2L99KaSlGXOukEtqk+l0JQcu ykoVk7o6NvOo2+zSEFph1jcBjMtWA4U4NgP4auRKGA3HNTxjIpZJWmcO4fr9a6RPRpc9 JfWy9zYwZBoavhBh2nwIE1PkGQtBQq2NCMqPgzKMNT9pR3FyMD8w8P0Q2CZctCHSqloM mgHg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684342418; x=1686934418; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=tjPxfbv5LVG91A9E+cywnl5RYdep2vWpj93tE4eNZR8=; b=k66s4VUSWSh8/BebxAnV687DXBTGC8awmGbw9j/oTbPKtLsc2nSF6+j0W4SnfzEY56 IfY0lSr/aaEYysT5YGGUny/cNA8aknTZxL2bUmkC0LOq+58rkOXFFjUnLCPst9saNXo2 LVnChOwm2MaWepejJd18UnsAGXv3g/FLAPIZ8HFGCbNYkhRzV7zud0iYTO70zWXI3nra uHM41H56F1vN3RDBJ/LXh3towCZg7wUpEZQBdiH1PmEcwhdL2CnJEi8baAstTNx3iUMc w3BpS+JH1wrY6ETmxTAYpIEnIdsDR7bELHlYLlpqhaqWOKbhjlAYpu5lsCDQPkVwQ1KV ff7g== X-Gm-Message-State: AC+VfDxtL0pgG1yxQusQl03DDot/wMy3iZx53tehbWet8Pb9CTZuAyot TqsClCIuY3Zue6cs0FouDsA= X-Google-Smtp-Source: ACHHUZ46nRh46vGSPymmf1lZUcqswH+JS2MYiE6NIBEn8vUt/1iP6exahk+6g7gdKaSDf51Jeb/RDQ== X-Received: by 2002:a17:902:cec9:b0:19a:a9d8:e47f with SMTP id d9-20020a170902cec900b0019aa9d8e47fmr58748542plg.36.1684342418223; Wed, 17 May 2023 09:53:38 -0700 (PDT) Original-Received: from [192.168.1.2] (cpe-76-168-148-233.socal.res.rr.com. [76.168.148.233]) by smtp.googlemail.com with ESMTPSA id y16-20020a17090322d000b001acaf7e26bbsm15911163plg.53.2023.05.17.09.53.37 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 17 May 2023 09:53:37 -0700 (PDT) Content-Language: en-US In-Reply-To: <83bkijxenf.fsf@gnu.org> X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:261868 Archived-At: 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.