1 .TH zpm 8 2019-02-15 "ZPM 0.3"
3 zpm \- the ultimate package manager
12 zpm is the ultimate package manager.
13 The zpm program itself searches the pathfor zpm sub-commands to run.
14 Sub-commands will either be statically linked compiled programs.
16 ZPM stores packages and package information in zpm databases, which
17 are sqlite3 databases with an application id of 0x5a504442. The
18 current user_version is 1. Both packages and information about installed
19 package are stored in zpm databases, with an identical database schema.
20 The difference between them is in how they are used and what they
24 Packages are identified by a name-version-release triple.
26 The name is the general name of the package, which must start with a letter,
27 and may contain letters, numbers, or a '-'.
29 The version must start with a numeral, and may contain numerals, letters, and
30 '.'. The version generally matches the upstream version of the software
31 in the package, but may be different due to the format requirements or
32 as assigned by the packager.
34 The release is a decimal integer assigned by the packager.
36 Usually a package may be specified by name or name and version if those
37 are unique for the context.
40 Package metadata is collected into stream and hashed with sha256 to
41 create a package hash. This hash may be verified by the admin,
42 and may be signed by the packager.
45 Packages can be signed by the zpm-sign utility.
47 Public keys are put into a trust db at /var/lib/zpm/trustdb
48 (or $ZPMTRUSTDB, or ~/.zpm/trustdb, or via command line).
50 zpm-checksignature -t trustdbfile
52 ZPM understands ELF files, and will automatically calculate elf library
55 \-P \fIpath\fR sets a path to the sub-command executables
57 .B zpm init \fIpkgfile\fR
58 .B zpm list \fIpkgfile\fR
62 Many commands take a database to work on. If not specified via a command
63 line option, a path to the database is taken from the ZPMDB environment
64 variable of, if that is not set, /var/lib/zpm/local.db is used.
66 0 on success non zero on failure
73 The following code all has a statement putting it into the public domain.
76 adapted from code by Phillip Lay https://www.phlay.de/
79 TLS code adapted from tlse (heavily, there really isn't much tlse code left).
81 tomsfastmath and libtomcrypt
82 used by the TLS implementation
84 Chacha20 and Curve25519
85 from ref10 implementations by Daniel Bernstein
88 from https://sqlite.org/index.html
91 from http://git.tukaani.org/xz.git
94 taken from http://mxr.mozilla.org/mozilla/source/security/nss/lib/ckfw/builtins/certdata.txt
96 All other code written by Nathan Wagner and also placed in the public domain.
98 ZPM itself is in the public domain. Compiled programs themselves
99 likely contain code from the C library and are subject to any licensing
100 requirements that implies. Where possible, programs have been statically
101 linked with musl rather than glibc, since glibc doesn't actually support
102 static linking. For the musl copyright see https://git.musl-libc.org/cgit/musl/tree/COPYRIGHT.
114 .BR zpm-packagehash (8)
118 .BR zpm-rmpackage (8)