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

GRID-CA-PACKAGE(1)						  Globus Commands						GRID-CA-PACKAGE(1)

NAME
grid-ca-package - Prepare a CA certificate, configuration, and policy for distribution SYNOPSIS
grid-ca-package [-help] [-h] [-usage] [-version] [-versions] grid-ca-package [-ca HASH] [-g] [-b] [-r] [-d] DESCRIPTION
The grid-ca-package utility creates a tarball containing an RPM spec file and the files needed to use a CA with grid tools. It optionally will also create a GPT package for distributing a CA. By default, the grid-ca-package utility displays a list of installed grid CA and prompts for which CA to package. It then creates a tarball containing the CA certificate, signing policy, CA configuration files, and an spec script to generate a binary RPM package containing the CA. If the CA hash is known prior to running grid-ca-package, it may provided as an argument to the -ca parameter to avoid prompting. In addition to generating a spec script and tarball, grid-ca-package creates a GPT package if either the -g or -b options are used on the command-line. These packages may be used to distribute a CA and configuration to systems which do not support RPM packages. The grid-ca-package utility writes the package tarballs to the current working directory. The full set of command-line options to grid-ca-package follows. -help, -h, -usage Display the command-line options to grid-ca-package and exit. -version, -versions Display the version number of the grid-ca-package command. The second form includes more details. -ca CA Use the CA whose name matches the hash string CA. When invoked with this option, grid-ca-package runs non-interactively. -g Create a GPT binary package in addition to the RPM script tarball. This package may be installed on other systems using the gpt-install program. -b Create a GPT binary package with GPT metadata located in the path expected by GPT 3.2 (used in Globus 2.0.0-5.0.x) instead of ${datadir}/globus/packages as used in Globus 5.2.x. This option overrides the -g command-line option. -r Create a binary RPM package for the CA. This option currently only works on RPM-based distributions. -d Create a binary Debian package for the CA. This option currently only works on Debian-based distributions. EXAMPLES
Package a Simple CA with hash 0146c503 % grid-ca-package -ca 0146c503 Creating RPM source tarball... done globus_simple_ca_0146c503.tar.gz ENVIRONMENT VARIABLES
The following environment variables affect the execution of grid-ca-package: GLOBUS_LOCATION Non-standard installation path of the Globus toolkit. SEE ALSO
grid-cert-request(1), grid-ca-sign(1), grid-default-ca(1), grid-ca-create(1) AUTHOR
University of Chicago Globus Toolkit 5.2.0 07/22/2011 GRID-CA-PACKAGE(1)
Man Page