From f965f35b33b7d722b34796823012dcd2a06ae0bd Mon Sep 17 00:00:00 2001 From: Dmitry Gutov Date: Mon, 24 Apr 2023 02:00:54 +0300 Subject: Rename all functions called package-*-update-* to package-*-upgrade-* * lisp/emacs-lisp/package-vc.el (package-vc-upgrade-all): Rename from 'package-vc-update-all'. (package-vc-upgrade): Rename from 'package-vc-update'. * lisp/emacs-lisp/package.el (package-upgrade): Rename from 'package-update' (bug#62750). (package--upgradeable-packages): Rename from 'package--updateable-packages'. (package-upgrade-all): Rename from 'package-update-all'. --- doc/emacs/package.texi | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'doc') diff --git a/doc/emacs/package.texi b/doc/emacs/package.texi index 2b03399b0a7..d1766026db2 100644 --- a/doc/emacs/package.texi +++ b/doc/emacs/package.texi @@ -329,15 +329,15 @@ version of the package, a newer version is also installed. @section Package Installation @findex package-install -@findex package-update -@findex package-update-all +@findex package-upgrade +@findex package-upgrade-all Packages are most conveniently installed using the package menu (@pxref{Package Menu}), but you can also use the command @kbd{M-x package-install}. This prompts for the name of a package with the @samp{available} status, then downloads and installs it. Similarly, -if you want to update a package, you can use the @kbd{M-x -package-update} command, and if you just want to update all the -packages, you can use the @kbd{M-x package-update-all} command. +if you want to upgrade a package, you can use the @kbd{M-x +package-upgrade} command, and if you want to upgrade all the packages, +you can use the @kbd{M-x package-upgrade-all} command. @cindex package requirements A package may @dfn{require} certain other packages to be installed, @@ -551,8 +551,8 @@ bugs. source code for a package directly from source. The command will also automatically ensure that all files are byte-compiled and auto-loaded, just like with a regular package. Packages installed this way behave -just like any other package. You can update them using -@code{package-update} or @code{package-update-all} and delete them +just like any other package. You can upgrade them using +@code{package-upgrade} or @code{package-upgrade-all} and delete them again using @code{package-delete}. They are even displayed in the regular package listing. If you just wish to clone the source of a package, without adding it to the package list, use -- cgit v1.2.1