expand docs

[zpackage] / doc / zpm-update.8

diff --git a/doc/zpm-update.8 b/doc/zpm-update.8
index 301ef6035f90e639600c835e022478e889071880..4f10ca6037f6bed57e28ec62dad11a925d006b1c 100644 (file)
--- a/doc/zpm-update.8
+++ b/doc/zpm-update.8
@@ -9,14 +9,6 @@ zpm-update \- update set of installed packages
 [
 .B -LAOUnzvpSC
 ]
-               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