ACPIDUMP(8) - System Manager’s Manual # ACPIDUMP(8) - System Manager’s Manual
NAME # acpidump - dump ACPI tables
SYNOPSIS # acpidump -o prefix
DESCRIPTION # The acpidump command stores ACPI tables from physical memory into files specified by prefix. If prefix specifies a directory, the generated files will be of the form <prefix>/<sig>.<id>. Otherwise, they will be named <prefix>.<sig>.<id>. “sig” is the signature of the ACPI Table; “id” is unique for each table.
...
Ports,
Bsd.port.arch.mk,
Distfiles,
Pkg_add,
Modules,
Intro,
Mk.conf,
Specs,
Pkgpath,
Ftp,
Pkg_create,
Bsd-Port-Mk BSD.PORT.MK(5) - File Formats Manual # BSD.PORT.MK(5) - File Formats Manual
NAME # bsd.port.mk - ports tree master Makefile fragment
SYNOPSIS # .include <bsd.port.mk>
DESCRIPTION # bsd.port.mk contains the [ports(7)](/man/man7/ports.7) tree make(1) framework, in the form of documented public targets, variables and paths.
The actual bsd.port.mk file lives under ${PORTSDIR}/infrastructure/mk, with make(1)’s system include file redirecting to it.
Optional parts of this framework have been moved to port-modules(5) in an effort to shrink the main file (see also MODULES) .
...
BUILD-DEBUG-INFO(1) - General Commands Manual # BUILD-DEBUG-INFO(1) - General Commands Manual
NAME # build-debug-info - generate packing-lists and Makefiles for debug packages
SYNOPSIS # PORTSDIR=path
build-debug-info [-mnqvx] -P pkgdir – pkg_create_args …
DESCRIPTION # build-debug-info is a helper script for generating debug package information in bsd.port.mk(5), with similar calling conventions to update-plist(1).
Along with options and environment variables, build-debug-info uses the exact same options and arguments that would be passed to pkg_create(1).
...
FW_UPDATE(8) - System Manager’s Manual # FW_UPDATE(8) - System Manager’s Manual
NAME # fw_update - install non-free firmware packages
SYNOPSIS # fw_update [-adFnv] [-p path] [driver | file …]
DESCRIPTION # The fw_update utility installs, updates, or deletes firmware packages for driver from the Internet. If no driver is specified, the fw_update utility tries to determine which firmware is needed on the system.
Since firmware with an acceptable license is already present in OpenBSD, fw_update exists purely to deal with firmware that may not be freely distributed with OpenBSD.
...
INSTALLURL(5) - File Formats Manual # INSTALLURL(5) - File Formats Manual
NAME # installurl - OpenBSD mirror server location
DESCRIPTION # The /etc/installurl file contains a single line specifying an OpenBSD mirror server URL, such as
https://cdn.openbsd.org/pub/OpenBSD It is created by the installer script during installations and upgrades.
Empty lines and lines beginning with ‘#’ in the file are ignored.
FILES # /etc/installurl
SEE ALSO # pkg_add(1), syspatch(8), sysupgrade(8)
...
Depends,
Ports,
Ld,
Pkg_add,
Packages,
Specs,
Ld.so,
Helper,
Bsd.port.mk,
Ldconfig,
Library-Specs LIBRARY-SPECS(7) - Miscellaneous Information Manual # LIBRARY-SPECS(7) - Miscellaneous Information Manual
NAME # library-specs - shared library name specifications
DESCRIPTION # Each WANTLIB item in the ports tree conforms to
[path/]libname[=major[.minor]] or
[path/]libname[>=major[.minor]] All libraries that a package needs must be mentioned in that list. Except for system and X11 libraries, they all must be reachable through LIB_DEPENDS and RUN_DEPENDS, directly, or indirectly through recursive dependencies.
Conversely, the ports tree uses WANTLIB to check whether a given LIB_DEPENDS will be required at runtime for shared libraries, and thus turn it into a @depend line (see pkg_create(1)) .
...
PACKAGE(5) - File Formats Manual # PACKAGE(5) - File Formats Manual
NAME # package, packing-list, plist - format for OpenBSD binary packages and packing-lists
DESCRIPTION # Binary packages for OpenBSD can be created using pkg_create(1) and are usually manipulated using pkg_add(1), pkg_mklocatedb(1), or pkg_info(1).
The basic underlying format is an archive following the ustar specification that can be handled with tar(1) and compressed using gzip(1).
Package names always end in “.
...
PACKAGES-SPECS(7) - Miscellaneous Information Manual # PACKAGES-SPECS(7) - Miscellaneous Information Manual
NAME # packages-specs - binary package names specifications
DESCRIPTION # Each package has a name consisting of at most three parts:
stem-version[-flavors] The stem part identifies the package. It may contain some dashes, but its form is mostly conventional. For instance, japanese packages usually start with a ‘ja’ prefix, e.g., “ja-kterm-6.2.0”.
The version part starts at the first digit that follows a ‘-’, and goes on up to the following ‘-’, or to the end of the package name, whichever comes first.
...
PKG_CHECK-PROBLEMS(1) - General Commands Manual # PKG_CHECK-PROBLEMS(1) - General Commands Manual
NAME # pkg_check-problems - verify problems in package collections
SYNOPSIS # pkg_check-problems [-CDesv] [-d plist_dir] [-o output] [-p ports_dir] [pkgname …]
DESCRIPTION # pkg_check-problems is used to check a collection of packages for problems that cannot be noticed in individual packages, such as conflict and directory registration issues.
A conflict is a file that belongs to two distinct packages.
...
Pkg_delete,
Ports,
Package,
Pkg_add,
Specs,
Pkgpath,
Pkg_sign,
Pkg_info,
Bsd.port.mk,
Tar,
Pkg-Create PKG_CREATE(1) - General Commands Manual # PKG_CREATE(1) - General Commands Manual
NAME # pkg_create - create binary software package for distribution
SYNOPSIS # pkg_create [-mnQqSvx] [-A arches] [-B pkg-destdir] [-D name[=value]] [-L localbase] [-M displayfile] [-P pkgpath:pkgspec:default] [-U undisplayfile] [-u userlist] [-V n] [-W libspec] -d desc -D COMMENT=value -D FULLPKGPATH=value -D PORTSDIR=value -f packinglist -p prefix pkg-name
pkg_create -f packinglist
DESCRIPTION # The pkg_create command is normally used to create a binary package named pkg-name, for subsequent use with pkg_add(1), pkg_delete(1) and pkg_info(1).
...