From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Ruijie Yu via "Emacs development discussions." Newsgroups: gmane.emacs.devel Subject: Re: emacs-29 09d6070e56e: ; Improve and update documentation of built-in package upgrades Date: Fri, 12 May 2023 22:09:19 +0800 Message-ID: References: <168389483830.11157.3184734522033933329@vcs2.savannah.gnu.org> <20230512123358.9ECA4C21705@vcs2.savannah.gnu.org> Reply-To: Ruijie Yu Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="6121"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.11.3; emacs 30.0.50 Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri May 12 16:10:21 2023 Return-path: Envelope-to: ged-emacs-devel@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 1pxTTQ-0001Sr-Oi for ged-emacs-devel@m.gmane-mx.org; Fri, 12 May 2023 16:10:20 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1pxTSj-0001et-If; Fri, 12 May 2023 10:09:37 -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 1pxTSh-0001eI-Ku for emacs-devel@gnu.org; Fri, 12 May 2023 10:09:35 -0400 Original-Received: from netyu.xyz ([152.44.41.246] helo=mail.netyu.xyz) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1pxTSf-0004bt-Uw; Fri, 12 May 2023 10:09:35 -0400 Original-Received: from fw.net.yu.netyu.xyz ( [222.248.4.98]) by netyu.xyz (OpenSMTPD) with ESMTPSA id 58464e41 (TLSv1.3:TLS_AES_256_GCM_SHA384:256:NO); Fri, 12 May 2023 14:09:30 +0000 (UTC) In-reply-to: <20230512123358.9ECA4C21705@vcs2.savannah.gnu.org> Received-SPF: pass client-ip=152.44.41.246; envelope-from=ruijie@netyu.xyz; helo=mail.netyu.xyz X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:306087 Archived-At: Eli Zaretskii writes: > branch: emacs-29 > commit 09d6070e56ea21a5e9720bc619c439c09e5b2680 > Author: Eli Zaretskii > Commit: Eli Zaretskii > > ; Improve and update documentation of built-in package upgrades > > * doc/emacs/package.texi (Package Statuses, Package Menu) > (Package Installation): > * etc/NEWS: Document the options and caveats of upgrading built-in > packages. > --- > doc/emacs/package.texi | 50 +++++++++++++++++++++++++++++++++++++++++++++++--- > etc/NEWS | 7 +++++++ > 2 files changed, 54 insertions(+), 3 deletions(-) > [...] > +In addition, when this option is non-nil, built-in packages for which > +a new version is available in archives can be upgraded via the package > +menu produced by 'M-x list-packages'. If you do set this option > +non-nil, we recommend not to use the 'U' command, but instead to use > +'/ u' to show the packages which can be upgraded, and then unmark the > +built-in packages which you don't need to overwrite from the archives. > [...] When you run `/ u' on the package list buffer, you don't automatically mark anything for upgrading, so saying "unmark" out-of-the-blue is a bit strange to me. For reference, you "mark" upgrades by `U', and then "execute" all queued actions (upgrades, installs, deletions, etc) by `x'. `/ u' filters the list of packages to only those which are upgradable, and nothing else. Maybe we should say one of the following proof-of-concept changes? ... we recommend not to execute the 'x' command immediately after the 'U' command, but instead .... ... but instead to use '/ u' to show the packages which can be upgraded, and then mark the built-in packages which you are okay with upgrading from the archives. ... but instead to use '/ u' to show the packages which can be upgraded, then 'U' to mark all all upgradable packages, and then unmark the built-in packages which you don't need to overwrite .... Hope this helps. -- Best, RY