PKG_ADD(1) BSD Reference Manual PKG_ADD(1)
pkg_add - install software package distributions
pkg_add [-fIMNnqRSv] [-d mode] [-p prefix] [-t template] pkg-name [...]
The pkg_add command is used to extract packages that have been previously created with the pkg_create(1) command. Selected packages containing pre-compiled applications from MirPorts can be found on the MirOS FTP site or on the official MirOS CD. These packages are provided as a con- venience for quickly installing software that would otherwise need to be built manually. Note: System distribution files, e.g. base10.ngz, etc10.ngz, etc., are not packages and may not be installed using pkg_add. Package names may be specified as filenames (which normally consist of the package name itself plus the ".tgz", ".tar.gz", or ".tar" suffix) or an FTP location in the form of an URL. For example, the following is valid: pkg_add -v https://www.mirbsd.org/Pkgs/v10/i386/joe-3.1jupp9-0.cgz If the given package names are not found in the current working directo- ry, pkg_add will search for them in each directory named by the PKG_PATH environment variable. Specifying '-' as a package name causes pkg_add to read from the standard input. Alternatively, it is possible to add packages interactively from within the ftp client. For example, the following works: $ ftp ftp://ftp.openbsd.org/pub/OpenBSD/2.7/packages/i386/ 250 CWD command successful ftp> ls m* 227 Entering Passive Mode (129,128,5,191,164,73) 150 Opening ASCII mode data connection for m*. m4-1.4.tgz metamail-2.7.tgz mh-6.8.4.tgz mm-1.0.12.tgz mpeg_lib-1.2.1.tgz mpeg_play-2.4.tgz mpg123-0.59q.tgz mutt-0.95.7i.tgz 226 Transfer complete. ftp> get m4-1.4.tgz "|pkg_add -v -" Warning: Since the pkg_add command may execute scripts or programs con- tained within a package file, your system may be susceptible to "trojan horses" or other subtle attacks from miscreants who create dangerous packages. Be sure the specified package(s) are from trusted sources. The options are as follows: -d Use the displaying mode for showing messages: e Use the environment variable PAGER to determine the pager programme, or more(1) if undefined. m more(1) is the pager. l less(1) is the pager. This implies a stop (waiting for q) on every port. c cat(1) is the pager. This is the default behaviour. It should only be used for bulk unattended installs. -v Turn on verbose output. -I If an installation script exists for a given package, do not exe- cute it. -N Do not make backups of existing files. -n Don't actually install a package, just report the steps that would be taken if it was. -q This option is internally used by pkg_upgrade(1). -R Do not record the installation of a package. This means that you cannot deinstall it later, so only use this option if you know what you are doing! -f Force installation to proceed even if prerequisite packages are not installed or the requirements script fails. Although pkg_add will still try to find and auto-install missing prerequisite packages, a failure to find one will not be fatal. -p prefix Set prefix as the directory in which to extract files from a package. If a package has set its default directory, it will be overridden by this flag. Note that only the first @cwd directive will be replaced, since pkg_add has no way of knowing which directory settings are relative and which are absolute. It is rare in any case to see more than one directory transition made, but when such does happen and you wish to have control over all directory transitions, then you may then wish to look into the use of MASTER and SLAVE modes (see the -M and -S options). -t template Use template as the input to mkdtemp(3) when creating a "staging area". By default, this is the string /var/tmp/instmp.XXXXXX, but it may be necessary to override it (see CAVEATS). Be sure to leave some number of "X" characters for mkdtemp(3) to fill in with a unique ID. You can get a performance boost by setting the staging area template to reside on the same disk partition as target direc- tories for package file installation; often this is /usr. -M Run in MASTER mode. This is a very specialized mode for running pkg_add and is meant to be run in conjunction with SLAVE mode. When run in this mode, pkg_add does no work beyond extracting the package into a temporary staging area (see the -t option), read- ing in the packing list, and then dumping it (prefaced by the current staging area) to the standard output where it may be fil- tered by a program such as sed(1). When used in conjunction with SLAVE mode, it allows you to make radical changes to the package structure before acting on its contents. -S Run in SLAVE mode. This is a very specialized mode for running pkg_add and is meant to be run in conjunction with MASTER mode. When run in this mode, pkg_add expects the release contents to be already extracted and waiting in the staging area, the location of which is read as a string from the standard input. The com- plete packing list is also read from stdin, and the contents then acted on as normal. By default, when adding packages via FTP, the ftp(1) program operates in "passive" mode. If you wish to use active mode instead, set the FTPMODE environment variable to "active". If pkg_add consistently fails to fetch a package from a site known to work, it may be because the site does not support passive mode ftp correctly. This is very rare since pkg_add will try active mode ftp if the server refuses a passive mode connection.
pkg_add extracts each package's "packing list" into a special staging directory in /var/tmp (or PKG_TMPDIR if set - see CAVEATS section) and then runs through the following sequence to fully extract the contents of the package: 1. A check is made to determine if the package is already recorded as installed. If it is, installation is terminated. 2. A check is made to determine if the package conflicts (from @pkgcfl directives, see pkg_create(1)) with an already recorded as installed package. If it is, installation is terminated. 3. All package dependencies (from @pkgdep directives, see pkg_create(1)) are read from the packing list. If any of these re- quired packages are not currently installed, an attempt is made to find and install it; if the missing package cannot be found or in- stalled, the installation is terminated. 4. A staging area is created under /var/tmp, and the package is ex- tracted into the staging area. 5. If the package contains a require script (see pkg_create(1)), it is executed with the following arguments: pkg-name The name of the package being installed INSTALL Keyword denoting to the script that it is to run an installation requirements check (the keyword is useful only to scripts which serve multiple functions). If the require script exits with a non-zero status code, the instal- lation is terminated. 6. If the package contains an install script, it is executed with the following arguments: pkg-name The name of the package being installed. PRE-INSTALL Keyword denoting that the script is to perform any ac- tions needed before the package is installed. If the install script exits with a non-zero status code, the instal- lation is terminated. 7. The packing list is used as a guide for moving (or copying, as necessary) files from the staging area into their final locations. 8. If the package contains an mtreefile file (see pkg_create(1)), then mtree is invoked as: mtree -u -f mtreefile -d -e -p prefix where prefix is either the prefix specified with the -p flag or, if no -p flag was specified, the name of the first directory named by a @cwd directive within this package. 9. If an install script exists for the package, it is executed with the following arguments: pkg_name The name of the package being installed. POST-INSTALL Keyword denoting that the script is to perform any ac- tions needed after the package has been installed. 10. After installation is complete, a copy of the packing list, deinstall script, description, and display files are copied into /var/db/pkg/<pkg-name> for subsequent possible use by pkg_delete(1). Any package dependencies are recorded in the other packages' /var/db/pkg/<other-pkg>/+REQUIRED_BY file (if the environment vari- able PKG_DBDIR is set, this overrides the /var/db/pkg/ path shown above). 11. Finally, the staging area is deleted and the program terminates. The install and require scripts are called with the environment variable PKG_PREFIX set to the installation prefix (see the -p option above). This allows a package author to write a script that reliably performs some ac- tion on the directory where the package is installed, even if the user might change it with the -p flag to pkg_add.
PKG_PATH If a given package name cannot be found, the directories named by PKG_PATH are searched. It should contain a series of entries separated by colons. Each entry consists of a directory name. The current directory may be indicated im- plicitly by an empty directory name, or explicitly by a single period ('.'). PKG_DBDIR Where to register packages instead of /var/db/pkg. PKG_REFCNTDB Name of the file that contains the reference count database for directories. The default is PKG_DBDIR/shareddirs.db. PKG_TMPDIR Temporary area where packages will be extracted, instead of /var/tmp.
pkg_create(1), pkg_delete(1), pkg_info(1), mkdtemp(3), sysconf(3), mtree(8)
Jordan Hubbard Initial work and ongoing development. John Kohl NetBSD refinements. Thorsten Glaser MirOS adaptions. rcdb(3) based shared directory counting implementation.
Package extraction does need a temporary area that: • is big enough to hold the complete extracted package, • can hold executable scripts. pkg_add looks through PKG_TMPDIR, TMPDIR, /var/tmp, /tmp for such an area, in sequence. If TMPDIR and /var/tmp are mounted noexec, you must set PKG_TMPDIR to a suitable area, as pkg_add has no way to check for noexec status except by failing to run installation scripts. Starting from MirOS #8, package tools generate SVR4 CPIO archives with CRC by default. These files usually have the extension .cgz, but .tgz is also possible. If compressed with LZMA, they are called .clz or .cxz (LZMA2). Uncompressed packages ending in .cpio and .tar are also allowed, for debugging, or slow platforms where the package is later compressed on a fast machine.
Hard links between files in a distribution are only preserved if either (1) the staging area is on the same file system as the target directory of all the links to the file, or (2) all the links to the file are brack- eted by @cwd directives in the contents file, and the link names are ex- tracted with a single tar(1) command (not split between invocations due to exec argument-space limitations; this depends on the value returned by sysconf(_SC_ARG_MAX)). Sure to be others. MirOS BSD #10-current November 22, 2009 4
Generated on 2014-02-10 02:47:05 by $MirOS: src/scripts/roff2htm,v 1.79 2014/02/10 00:36:11 tg Exp $
These manual pages and other documentation are copyrighted by their respective writers;
their source is available at our CVSweb,
AnonCVS, and other mirrors. The rest is Copyright © 2002‒2014 The MirOS Project, Germany.
This product includes material provided by Thorsten Glaser.
This manual page’s HTML representation is supposed to be valid XHTML/1.1; if not, please send a bug report – diffs preferred.