From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: Adam Porter <adam@alphapapa.net>,
larsi@gnus.org, Eli Zaretskii <eliz@gnu.org>,
philipk@posteo.net, 62750@debbugs.gnu.org
Subject: bug#62750: 29.0.50; Commands 'package-update' and 'package-update-all' should be called '*-upgrade'
Date: Sun, 30 Apr 2023 21:55:17 -0400 [thread overview]
Message-ID: <jwvildczumy.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <c3a1c586-69ed-7129-365f-da7fd26c9b87@gutov.dev> (Dmitry Gutov's message of "Mon, 24 Apr 2023 21:54:58 +0300")
> That might also be the case when upgrading a package that some others
> depend on (newer version could also have macros deleted or renamed).
We try to make upgrades "safe", but there's usually no such effort the
other way around, so downgrading is definitely more risky in practice,
even though in theory things can break in all cases.
> Would "update" be a more proper term to cover both upgrading and
> downgrading?
I think if you specify the target version, then `package-install` sounds
about right (and I suspect it may already "work").
> Or that. We don't keep older versions around in ELPA anyway, so for
> now the question is moot.
Well, we do keep them some `elpa.gnu.org` but indeed the ELPA protocol
doesn't include any way to advertise them.
Stefan
next prev parent reply other threads:[~2023-05-01 1:55 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
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 [this message]
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=jwvildczumy.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=62750@debbugs.gnu.org \
--cc=adam@alphapapa.net \
--cc=dmitry@gutov.dev \
--cc=eliz@gnu.org \
--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.