From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Payas Relekar Newsgroups: gmane.emacs.bugs Subject: bug#63536: Feature Request Date: Wed, 17 May 2023 21:10:15 +0530 Message-ID: <87jzx7yn0p.fsf@gmail.com> References: <1553770628.2069339.1684237196253@mail.yahoo.com> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="10053"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.10.3; emacs 29.0.91 Cc: 63536@debbugs.gnu.org, andrewgoh95@yahoo.com.sg To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Wed May 17 19:45:15 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 1pzLD8-0002NE-UC for geb-bug-gnu-emacs@m.gmane-mx.org; Wed, 17 May 2023 19:45:14 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pzLCz-00064m-Bb; Wed, 17 May 2023 13:45:05 -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 1pzLCw-0005za-U1 for bug-gnu-emacs@gnu.org; Wed, 17 May 2023 13:45:03 -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 1pzLCw-0003kW-HK for bug-gnu-emacs@gnu.org; Wed, 17 May 2023 13:45:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1pzLCw-0003BA-Bh for bug-gnu-emacs@gnu.org; Wed, 17 May 2023 13:45:02 -0400 X-Loop: help-debbugs@gnu.org In-Reply-To: <1553770628.2069339.1684237196253@mail.yahoo.com> Resent-From: Payas Relekar Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 17 May 2023 17:45: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.168434548612187 (code B ref 63536); Wed, 17 May 2023 17:45:02 +0000 Original-Received: (at 63536) by debbugs.gnu.org; 17 May 2023 17:44:46 +0000 Original-Received: from localhost ([127.0.0.1]:50966 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pzLCg-0003AT-H5 for submit@debbugs.gnu.org; Wed, 17 May 2023 13:44:46 -0400 Original-Received: from mail-pl1-f171.google.com ([209.85.214.171]:56446) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1pzLCd-0003AD-V2 for 63536@debbugs.gnu.org; Wed, 17 May 2023 13:44:44 -0400 Original-Received: by mail-pl1-f171.google.com with SMTP id d9443c01a7336-1ae4be0b1f3so8865675ad.0 for <63536@debbugs.gnu.org>; Wed, 17 May 2023 10:44:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1684345478; x=1686937478; h=mime-version:message-id:date:subject:cc:to:from:user-agent:from:to :cc:subject:date:message-id:reply-to; bh=ziMj1hBRpYvXgG3S5Sp34JM3TQCcn1VpjAu/2FepPYQ=; b=gLuttRhnf9CYsEp0WWtCZU9heyWit6TS7x8jCTM0JZ+n6cwdTtZuZJ5r2mFNxDN+eV zH2fqqf+kHVocfpci4RZCfUAwHQYFLRUW20+O0zTGKeA0izwwWhDasgo6P2I31PgIElb vDlLX2zqMcZAw0DCltj4ovzDikVj4DXGl2nSssETdK/MRbECHlYNljpTI5LbBK69fRL/ JVJdSCjAdKWOKq1ygWcBIM1AspP2aXIHMD0DWHSdTCQ+gRQtQ7jj5jsfbhhNxTlAa2HD 06ebt400gcXTgxSQgDH9K0nZ94z/Uez7P62b0ebpXTfFI0OUsnDibFCumIyfHMPTZUDr olQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684345478; x=1686937478; h=mime-version:message-id:date:subject:cc:to:from:user-agent :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=ziMj1hBRpYvXgG3S5Sp34JM3TQCcn1VpjAu/2FepPYQ=; b=JbVe+Y6p6qvPsw4K+rtKj3bHobL6zTzNqS0uBYtvemnClsaqvH0LXafaHz2qahusgF 6kSTgdN7LcEPCG7x+bYf1oWhq7ISH1Hzcga+2ilWn6E5+UljL8lWQPFPwOlrVpFukopb E18OExlenZ9dCmaAMFBPTJk9vStIqWaHryYziElFOeT3tam2sIjnmpV9lBlBNoMosZXl NSLPwbAomAoRp29uSxBK5d9IbpGn/fZ0mIYT4XvUVnYT1RxX+AmF80RnZpL5oJKxItbT RSmJ5AH4lFm+VEsZ5LIS2EQsk2aqjs58FahX5YnqHokp4SJDU2/tyR2JxTRhSdiGX24z DqfQ== X-Gm-Message-State: AC+VfDz6JFyUW1pwQMbxpVCaHRi1qNDvk9GS+n7U4EeoN5Zt+KUV+C5t WIYYwElrNFAtqwZ1k+dplAA= X-Google-Smtp-Source: ACHHUZ5wcgZU1yys2DAnEqD7Ddk12WkPV9l6Af/3jM9p9/i71HEHEwaIgPMmKaF4j5y6h8k1eQ5GGw== X-Received: by 2002:a17:902:da85:b0:1ac:a887:d344 with SMTP id j5-20020a170902da8500b001aca887d344mr39329499plx.19.1684345477779; Wed, 17 May 2023 10:44:37 -0700 (PDT) Original-Received: from localhost (aipl-9-69-179-202.ankhnet.net. [202.179.69.9]) by smtp.gmail.com with ESMTPSA id n18-20020a170902d2d200b001aaeba5ce0fsm17884426plc.68.2023.05.17.10.44.36 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 17 May 2023 10:44:37 -0700 (PDT) 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:261879 Archived-At: Eli Zaretskii writes: >> From: Payas Relekar >> Cc: Andrew Goh , 63536@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. > > Another possible issue is whether just to tell the user "A newer > version XY.Z is available, you can download it at ", or also > offer a possibility of actually downloading the newer version? The former is preferred. Emacs users more often than not use third party mechanisms (e.g. package managers) to get it installed. Any action for actually downloading would muddy the waters. Here's the flow that I imagine: 1. User runs `M-x emacs-check-update` 2. Emacs checks GNU repo and provides somthing like: `Update for Emacs 29.1 is now available. Current version is 28.2. If you installed Emacs via a package manager like your GNU/linux distribution, homebrew, Guix etc, please follow their respective instructions. If you installed Emacs by compiling from source, follow _link to latest Emacs compilation instructions_. If you'd like to check for updates for Emacs-Lisp packages, please check 'package-upgrade'` 3. User chooses to follow or ignore the instructions. The wording would play big part, but as long as we make it clear to follow the path of original installation is preferred, I think most users can figure it out, just like the rest of the manual. At any point, Emacs providing built-in mechanism for update, while nice to have, will be gigantic pain to implement and even bigger pain to maintain. Something like rustup is well-desired, but Emacs has very broad scope and dependency tree unlike rust toolchain, so I'd rather avoid it. --