all messages for Emacs-related lists mirrored at yhetil.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 22:13:51 +0300	[thread overview]
Message-ID: <83ttx5w0sw.fsf@gnu.org> (raw)
In-Reply-To: <c3a1c586-69ed-7129-365f-da7fd26c9b87@gutov.dev> (message from Dmitry Gutov on Mon, 24 Apr 2023 21:54:58 +0300)

> Date: Mon, 24 Apr 2023 21:54:58 +0300
> Cc: monnier@iro.umontreal.ca, philipk@posteo.net, larsi@gnus.org,
>  62750@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
> 
> On 24/04/2023 20:28, Adam Porter wrote:
> > On 4/24/23 07:02, Eli Zaretskii wrote:
> > 
> >> 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.
> > 
> > IMHO, a command to downgrade ought to be a separate command with a 
> > different name--not only to reduce confusion, but because downgrading 
> > packages is an operation that is more likely to require manual user 
> > intervention, such as recompiling other packages that depend on the 
> > downgraded package (e.g. if struct or macro definitions change, or 
> > symbols disappear).
> 
> That might also be the case when upgrading a package that some others 
> depend on (newer version could also have macros deleted or renamed).
> 
> Either way, though, we could make it a separate command.

A separate command that does the same, or almost the same, as
package-upgrade?  That's uneconomical, let alone elegant.

> Or even augment the current one: (package-upgrade 'name 
> "some-older-version") has a similar feel to (forward-char -1), not 
> exactly unfamiliar to us.

We are talking about invoking commands, not about Lisp programs.  How
many times did you do "C-- C-f" instead of "C-b"?

> We don't keep older versions around in ELPA anyway, so for now the
> question is moot.

I was trying to raise a possible future issue.  We all know that
command names, once they gain enough tenure, cannot be easily changed.
So this is the time to think about future issues; we won't have
another chance.  It's exactly why we should consider what is today a
"moot point" but could be a real one later.





  reply	other threads:[~2023-04-24 19:13 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
2023-04-24 17:28                         ` Adam Porter
2023-04-24 18:54                           ` Dmitry Gutov
2023-04-24 19:13                             ` Eli Zaretskii [this message]
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=83ttx5w0sw.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 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.