expand verify

[zpackage] / doc / zpm-update.8

diff --git a/doc/zpm-update.8 b/doc/zpm-update.8
index 301ef6035f90e639600c835e022478e889071880..c25751e03edb8581bbdd43f93659672431d198b6 100644 (file)
--- a/doc/zpm-update.8
+++ b/doc/zpm-update.8
@@ -1,4 +1,4 @@
-.TH zpm-update 8 2018-12-10 "ZPM 0.4"
+.TH zpm-update 8 2019-02-16 "ZPM 0.4"
 .SH NAME
 zpm-update \- update set of installed packages
 .SH SYNOPSIS
@@ -7,16 +7,8 @@ zpm-update \- update set of installed packages
 .BI -f " pkgfile"
 ]
 [
-.B -LAOUnzvpSC
+.B -LAOUnzvpSCl
 ]
-               d) localdb="$OPTARG" ;;
-               P) packagepath="$OPTARG" ;;
-               D) packagepath="$OPTARG:$packagepath" ;;
-               R) rootdir="$OPTARG" ;;
-
-               b) backup=1 ;;
-               B) backup=0 ;;
-               l) justlist=1 ;;
 .RI [ \fB[+|-]\fIpackage ...]
 .SH DESCRIPTION
 \fBzpm-update\fR changes the set of installed packages.
@@ -46,6 +38,10 @@ In other words, all of the packages given are updated, removed, installed at
 the same time, rather than taking each package one at a time and installing,
 updating, or removing it.  If the admin wants to do the packages one at a time,
 zpm-update can be run multiple times.
+.PP
+Either the package update process, or package scripts may
+put notes in the database with information for the sysadmin.
+zpm-note should be run after updates to check for these.
 .SS Package Search
 Packages will be searched for in *.repo files, the local database, and
 in individual zpm package files.  These are looked for by default
@@ -62,6 +58,9 @@ and doesn't run any package scripts.  Since scripts aren't run
 and no files are changed, this can only detect and report some
 types of errors.
 .TP
+\-l
+Just list the computed set of packages to update.
+.TP
 \-R \fIrootdir\fR
 Specify a root directory for the package installs.  Files will be
 installed relative to this directory.