Send patches - preferably formatted by git format-patch - to patches at archlinux32 dot org.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/pacman.8.txt15
1 files changed, 12 insertions, 3 deletions
diff --git a/doc/pacman.8.txt b/doc/pacman.8.txt
index 249923a1..3d14a42a 100644
--- a/doc/pacman.8.txt
+++ b/doc/pacman.8.txt
@@ -90,8 +90,9 @@ to determine which packages need upgrading. This behavior operates as follows:
*-U, \--upgrade*::
Upgrade or add package(s) to the system and install the required
dependencies from sync repos. Either a URL or file path can be
- specified. This is a ``remove-then-add'' process. See <<HCF,Handling Config
- Files>> for an explanation on how pacman takes care of config files.
+ specified. This is a ``remove-then-add'' process. See <<UO,Upgrade
+ Options>> below; also see <<HCF,Handling Config Files>> for an explanation
+ on how pacman takes care of config files.
*-V, \--version*::
Display version and exit.
@@ -273,7 +274,7 @@ Remove Options[[RO]]
or more target packages. This operation is recursive, and must be used
with care since it can remove many potentially needed packages.
-*-k, \--keep*::
+*-k, \--dbonly*::
Removes the database entry only. Leaves all files in place.
*-n, \--nosave*::
@@ -375,6 +376,14 @@ linkman:pacman.conf[5].
separating them with a comma.
+Upgrade Options[[UO]]
+--------------------
+*-k, \--dbonly*::
+ Adds the database entries for the specified packages but do not install any
+ of the files. On an upgrade operation, the existing package and all files
+ will be removed and the database entry for the new package will be added.
+
+
Handling Config Files[[HCF]]
----------------------------
Pacman uses the same logic as rpm to determine action against files that are