all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Adam Porter <adam@alphapapa.net>
To: 62750@debbugs.gnu.org
Subject: bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade'
Date: Mon, 10 Apr 2023 07:53:52 -0500	[thread overview]
Message-ID: <2726a957-a2a8-3b89-8930-2d620d83491e@alphapapa.net> (raw)

Hi,

Browsing the NEWS file for the first Emacs 29 pretest, I was glad to see
the following new commands:

     +++
     *** New command 'package-update'.
     This command allows you to upgrade packages without using 'M-x
     list-packages'.

     +++
     *** New command 'package-update-all'.
     This command allows updating all packages without any queries.

But, IMHO, these commands should be named 'package-upgrade' and
'package-upgrade-all'.

In my experience in GNU/Linux systems and other software, the verb
"update" is commonly used to refer to updating the list of available
packages and their versions without changing the installed versions of
packages (e.g. in Debian, "apt update"), while the verb "upgrade" is
used to refer to actually installing newer versions of packages
(e.g. "apt upgrade", or GNU Guix's "guix upgrade").  This terminology 
mirrors the inverse, i.e. "downgrading"; it's not said that packages are 
"downdated" or "backdated."

Even the first NEWS entry seems to suggest this conflation, as it says,
"This command allows you to upgrade packages...".

If it's not too late to make this change, I think it would be
worthwhile, as I think it would help prevent confusion for many users.
OTOH, if Emacs 29 is released with "update packages" meaning "to upgrade
packages to newer versions", we may be stuck with this confusing
language for a long time.

Thanks for your consideration, and for your work on Emacs.





             reply	other threads:[~2023-04-10 12:53 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-10 12:53 Adam Porter [this message]
2023-04-10 13:18 ` bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade' Eli Zaretskii
2023-04-10 13:25   ` Philip Kaludercic
2023-04-10 14:31     ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-11 21:28       ` Dmitry Gutov
2023-04-11 21:40         ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12  7:35           ` Philip Kaludercic
2023-04-12 13:22             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-12 13:28               ` Eli Zaretskii
2023-04-12 13:34                 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-15  1:34                   ` Dmitry Gutov
2023-04-23 23:06                     ` Dmitry Gutov
2023-04-24 12:02                       ` Eli Zaretskii
2023-04-24 17:28                         ` Adam Porter
2023-04-24 18:54                           ` Dmitry Gutov
2023-04-24 19:13                             ` Eli Zaretskii
2023-04-24 19:38                               ` Dmitry Gutov
2023-05-01  1:55                             ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-05-01 13:19                               ` Dmitry Gutov
2023-04-12 13:44               ` Philip Kaludercic
2023-04-12 14:36                 ` João Távora
2023-04-19 22:23         ` Jim Porter
2023-04-27 23:27 ` Dmitry Gutov
2023-04-28 14:26   ` Philip Kaludercic

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=2726a957-a2a8-3b89-8930-2d620d83491e@alphapapa.net \
    --to=adam@alphapapa.net \
    --cc=62750@debbugs.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.