Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

pkg_summary(5) [netbsd man page]

PKG_SUMMARY(5)						      BSD File Formats Manual						    PKG_SUMMARY(5)

NAME
pkg_summary -- summary of binary package repository DESCRIPTION
The file pkg_summary contains information about each package in a binary package repository as a list of variable-value pairs. The variables describing different packages are separated by one empty line. Each line has the format VARIABLE=VALUE. If the value consists of more than one line, each line is prefixed with VARIABLE=. Multi-line variables are guaranteed to be in consecutive lines. The following variables are used: BUILD_DATE (required) The date and time when the package was built. CATEGORIES (required) A list of categories which this package fits in, separated by space. COMMENT (required) A one-line description of the package. CONFLICTS (optional) A list of dewey patterns of packages the package conflicts with, one per line. If missing, this package has no conflicts. DEPENDS (optional) A list of dewey patterns of packages the package depends on, one per line. If missing, this package has no dependencies. DESCRIPTION (required) A more detailed description of the package. FILE_CKSUM (optional) A checksum type supported by digest(1) and checksum separated by space character. FILE_NAME (optional) The name of the binary package file. If not given, PKGNAME.tgz can be assumed. FILE_SIZE (optional) The size of the binary package file, in bytes. HOMEPAGE (optional) A URL where more information about the package can be found. LICENSE (optional) The type of license this package is distributed under. If empty or missing, it is OSI-approved. MACHINE_ARCH (required) The architecture on which the package was compiled. OPSYS (required) The operating system on which the package was compiled. OS_VERSION (required) The version of the operating system on which the package was compiled. PKG_OPTIONS (optional) Any options selected to compile this package. If missing, the package does not support options. PKGNAME (required) The name of the package. PKGPATH (required) The path of the package directory within pkgsrc. PKGTOOLS_VERSION (required) The version of the package tools used to create the package. PREV_PKGPATH (optional) The previous path of the package directory within pkgsrc when a package was moved. (See SUPERSEDES below for a renamed package.) PROVIDES (optional) A list of shared libraries provided by the package, including major version number, one per line. If missing, this pack- age does not provide shared libraries. REQUIRES (optional) A list of shared libraries needed by the package, including major version number, one per line. If missing, this package does not require shared libraries. SIZE_PKG (required) The size of the package when installed, in bytes. SUPERSEDES (optional) A list of dewey patterns of previous packages this package replaces, one per line. This is used for package renaming. The pkg_summary file can be generated using the pkg_info(1) -X option. For example, the following will list this data for all installed packages: pkg_info -X -a SEE ALSO
digest(1), pkg_info(1) HISTORY
The pkg_summary format was first officially documented in April 2006. BSD
April 11, 2009 BSD

Check Out this Related Man Page

DD-LIST(1)						      General Commands Manual							DD-LIST(1)

NAME
dd-list - nicely list .deb packages and their maintainers SYNOPSIS
dd-list [-hiusV] [--help] [--stdin] [--sources Sources_file] [--dctrl] [--version] [--uploaders] [package ...] DESCRIPTION
dd-list produces nicely formatted lists of Debian (.deb) packages and their maintainers. Input is a list of source or binary package names on the command line (or the standard input if --stdin is given). Output is a list of the following format, where package names are source packages by default: J. Random Developer <jrandom@debian.org> j-random-package j-random-other Diana Hacker <diana@example.org> fun-package more-fun-package This is useful when you want, for example, to produce a list of packages that need to attention from their maintainers, e.g., to be rebuilt when a library version transition happens. OPTIONS
-h, --help Print brief help message. -i, --stdin Read package names from the standard input, instead of taking them from the command line. Package names are whitespace delimited. -d, --dctrl Read package list from standard input in the format of a Debian package control file. This includes the status file, or output of apt-cache. This is the fastest way to use dd-list, as it uses the maintainer information from the input instead of looking up the maintainer of each listed package. If no Source: line is given, the Package: name is used for output, which might be a binary package name. -s, --sources Sources_file Read package information from the specified Sources_files. This can be given multiple times. If no Sources_files are specified, any files matching /var/lib/apt/lists/*_source_Sources will be used. -u, --uploaders Also list developers who are named as uploaders of packages, not only the maintainers; this is the default behaviour, use --nou- ploaders to prevent it. Uploaders are indicated with "(U)" appended to the package name. -nou, --nouploaders Only list package Maintainers, do not list Uploaders. -b, --print-binary Use binary package names in the output instead of source package names (has no effect with --dctrl if the Package: line contains source package names). -V, --version Print the version. AUTHOR
Lars Wirzenius <liw@iki.fi> Joey Hess <joeyh@debian.org> Debian 2011-10-27 DD-LIST(1)
Man Page