unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: adam@alphapapa.net, larsi@gnus.org, philipk@posteo.net,
	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, 24 Apr 2023 15:02:42 +0300	[thread overview]
Message-ID: <83bkjdxzbx.fsf@gnu.org> (raw)
In-Reply-To: <eedb8cf7-085a-b207-b08d-29d18726bee5@gutov.dev> (message from Dmitry Gutov on Mon, 24 Apr 2023 02:06:45 +0300)

> Date: Mon, 24 Apr 2023 02:06:45 +0300
> From: Dmitry Gutov <dmitry@gutov.dev>
> Cc: adam@alphapapa.net, philipk@posteo.net, larsi@gnus.org,
>  62750@debbugs.gnu.org
> 
> Here's a couple of other existing functions:
> 
>    package--update-selected-packages
>    package--update-downloads-in-progress
> 
> Neither of these relate to upgrading packages. Although the former could 
> be easy to mistake for that now.
> 
> In all older functions, the term "update" (in comments and variable 
> names) refers to updating the value of some variable, not packages.
> 
> By analogy, 'M-x package-update-all' might be easy enough to mistake for 
> updating the list of packages available for installation, for example.
> 
> Here's a patch that does the rename. Also including package-vc-update* 
> that Philip mentioned.

Any objections to these renames, anyone?

Does anyone think we need to leave behind aliases for the old names?

Me, I have only one potential issue: since "update" just means "delete
the installed version, then install another version", it could be
easily made to downgrade, not just to upgrade.  So if we ever would
like to allow downgrading, the new names will get in the way.  But if
this is not an issue we should be bothered about, it's fine by me.

Thanks.





  reply	other threads:[~2023-04-24 12:02 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
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 [this message]
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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83bkjdxzbx.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62750@debbugs.gnu.org \
    --cc=adam@alphapapa.net \
    --cc=dmitry@gutov.dev \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=philipk@posteo.net \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).