GNU bug report logs - #62750
29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade'

Previous Next

Full log

Message #38 received at 62750 <at> debbugs.gnu.org (full text, mbox):

From: João Távora <joaotavora <at> gmail.com>
To: Philip Kaludercic <philipk <at> posteo.net>
Cc: 62750 <at> debbugs.gnu.org, Dmitry Gutov <dmitry <at> gutov.dev>,
 Stefan Monnier <monnier <at> iro.umontreal.ca>, Adam Porter <adam <at> alphapapa.net>,
 Eli Zaretskii <eliz <at> gnu.org>, Lars Ingebrigtsen <larsi <at> gnus.org>
Subject: Re: bug#62750: 29.0.50; Commands 'package-update' and
 'package-update-all' should be called '*-upgrade'
Date: Wed, 12 Apr 2023 15:36:52 +0100

On Wed, Apr 12, 2023 at 2:45 PM Philip Kaludercic <philipk <at> posteo.net> wrote:
>
> Stefan Monnier <monnier <at> iro.umontreal.ca> writes:
>
> >>> It's annoyingly late to rename, but if we rename without compatibility
> >>> aliases (which seems to be an option since these are new in Emacs-29),
> >>> then I'd be in favor.
> >>
> >> What are compatibility aliases?  I must have missed something?
> >
> > I thought we'd rename `package-update` to `package-upgrade` by adding
> > the new name and marking the old name as an obsolete alias (a
> > "compatibility alias").
> >
> > I hadn't realized that `package-update` hasn't been in a release yet, so
> > we don't need such a compatibility alias.
>
> If this were to happen, I'd like to also be able to rename the analogous
> package-vc commands to upgrade as well.
>
> (On a related topic I have been wondering if package-update should
> handle package-vc packages at all, or if that was a mistake?)

Also, in the off-chance that no-one has noticed yet the new
package-update-*commands and the older package-menu*upgrade
commands use entirely different logic to discover what _can_
be updated.  Only by sheer skill or luck will this logic match exactly.

João

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.