From: Philip Kaludercic <philipk@posteo.net>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Adam Porter <adam@alphapapa.net>,
Lars Ingebrigtsen <larsi@gnus.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
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 13:25:04 +0000 [thread overview]
Message-ID: <875ya3euof.fsf@posteo.net> (raw)
In-Reply-To: <83sfd7c1v1.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 10 Apr 2023 16:18:10 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Mon, 10 Apr 2023 07:53:52 -0500
>> From: Adam Porter <adam@alphapapa.net>
>>
>> +++
>> *** 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'.
>
> These commands exist for the last year. I'm not sure how reasonable
> it is to rename them now, they are probably used in umpteen places
> outside Emacs already. Maybe if we leave behind an alias.
>
> And what if someone teaches these commands to downgrade as well, at
> some future time?
>
> Does anyone else have an opinion? Lars, Stefan, Philip?
I don't think that "update" and "upgrade" have that clear of a semantic
difference in practice to necessitate a renaming. E.g. Debian's "apt"
distinguishes between updating (ie. synchronising the local repository
state) and upgrading (fetching and installing newer versions of a
package), while Fedora's dnf bundles both into one step and refers to it
as updating.
The term "update" probably has a minor edge over "upgrade" since it is a
more popular term, that users are more likely to search for.
next prev parent reply other threads:[~2023-04-10 13:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-10 12:53 bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade' Adam Porter
2023-04-10 13:18 ` Eli Zaretskii
2023-04-10 13:25 ` Philip Kaludercic [this message]
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=875ya3euof.fsf@posteo.net \
--to=philipk@posteo.net \
--cc=62750@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
/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.