1 .TH zpm-update 8 2019-02-19 "ZPM 0.4"
3 zpm-update \- update set of installed packages
12 .RI [ \fB[+|-]\fIpackage ...]
14 \fBzpm-update\fR changes the set of installed packages.
15 It can install, remove, or update a set of packages as given on the command
16 line. It will search defined repositories for packages, and download, merge,
17 and prepare the packages and the local database. By itself, zpm-update just
18 prepares the system for the file operations and runs package scripts. Actual
19 filesystem actions (i.e. removing or installing of files in the file system)
20 is delegated to zpm-syncfs.
22 Packages may be specified by a full package id triple, or any
23 shortened version of one (i.e. a package may be given by name, name
24 and version, or name, version, and release).
26 Packages may have an optional '+' or '-' prefix. Packages
27 marked with '+' are set to be installed, or updated if a package
28 with the same name is already installed. Packages marked with
29 a '-' are set to be uninstalled if they are installed.
30 By default, unmarked packages are treated as marked with a '+'.
31 The default can be changed to uninstall with the \fB-U\fR option.
33 Once the set of packages to installed or uninstalled is determined and set up,
34 zpm-syncfs is called to do the actual file operations. This is an
35 "all-at-once" action in the sense that the whole set of file actions is
36 considered and no concern is given to which specific package a file belongs to.
37 In other words, all of the packages given are updated, removed, installed at
38 the same time, rather than taking each package one at a time and installing,
39 updating, or removing it. If the admin wants to do the packages one at a time,
40 zpm-update can be run multiple times.
42 Either the package update process, or package scripts may
43 put notes in the database with information for the sysadmin.
44 zpm-note should be run after updates to check for these.
46 Packages will be searched for in *.repo files, the local database, and
47 in individual zpm package files. These are looked for by default
48 in /var/lib/zpm/*.repo /var/lib/zpm/packages/*.zpm and the usual
49 location for the local database.
53 specify the package file to find packages in
56 perform a dry run. This option calls zpm-syncfs in dry-run mode,
57 and doesn't run any package scripts. Since scripts aren't run
58 and no files are changed, this can only detect and report some
62 Just list the computed set of packages to update.
65 Specify a root directory for the package installs. Files will be
66 installed relative to this directory.
69 Don't run any package pre or post scripts. Normally zpm-update will run
70 package pre and post scripts associated with packages being removed, updated,
71 or installed. See zpm-script(8) for details. If any scripts are skipped due
72 to the option, a note will be added.
75 Don't run package configure scripts. Any skipped scripts will have a note
79 Run syncfs in verbose mode. This flag is passed on to zpm-syncfs.
82 Passed to zpm-syncfs to control the type of progress meter.
85 Don't pull remote repositories before searching for packages, by
86 default all remote repos are refreshed with repo pull before
87 commencing a search for new packages.
90 Don't check for library dependencies, passed on to zpm-search.
93 run zpm-syncfs in accept mode
96 run zpm-syncfs in overwrite mode mode
99 Treat unmarked packages as packages to be uninstalled.
103 Install or update the vim package to the latest package found.
106 Uninstall the vim package if it installed. The '--' is necessary
107 to the system doesn't think you are passing a -v option to zpm update.
110 Uninstall the vim package if it installed.
113 Install or update ed to the latest version available, and remove
116 0 on success non zero on failure
118 /var/lib/zpm/local.db