BSD.PORT.ARCH.MK(5) - File Formats Manual # BSD.PORT.ARCH.MK(5) - File Formats Manual
NAME # bsd.port.arch.mk - ports tree Makefile fragment, concerned with arch issues
SYNOPSIS # # Set up such as MULTI_PACKAGES = -main -special ONLY_FOR_ARCHS-special = i386 .include <bsd.port.arch.mk>
#some more lines such as .if ${BUILD_PACKAGES:M-special} CONFIGURE_ARGS += --enable-special .endif .include <bsd.port.mk>
DESCRIPTION # bsd.port.arch.mk holds the logic used for arch-dependent builds in the ports tree. It is normally included as part of the larger bsd.
...
BSD.REGRESS.MK(5) - File Formats Manual # BSD.REGRESS.MK(5) - File Formats Manual
NAME # bsd.regress.mk - regression test master Makefile fragment
SYNOPSIS # .include <bsd.regress.mk>
DESCRIPTION # bsd.regress.mk holds the standard routines used by the source regression tests. Some variables and targets are for its internal use only. The rest are documented here.
Since this file also includes bsd.prog.mk, all of the usual OpenBSD Makefile variables may be used to build the regression test programs.
...
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).
...
BULK(8) - System Manager’s Manual # BULK(8) - System Manager’s Manual
NAME # bulk - building OpenBSD packages in bulk
DESCRIPTION # There are quite a few steps necessary to build packages on a cluster. They are:
Choose master machine setup and create partitions. Setup chrooted builds on the master. Add slaves and do a full bulk. Clean up and do subsequent bulks. Perform additional maintenance. 1. Choose master machine setup and create partitions # Setup a master machine with enough room for a chroot, say /build.
...
CHECK-LIB-DEPENDS(1) - General Commands Manual # CHECK-LIB-DEPENDS(1) - General Commands Manual
NAME # check-lib-depends - scan port for shared libraries
SYNOPSIS # check-lib-depends [-fimqx] [-B destdir] [-d pkgrepo] [-D directory] [-F missing] [-O dest] [-S VAR=value] [-s source] [package …]
DESCRIPTION # check-lib-depends scans a port or package for shared libraries, and verify that all of them are properly recorded.
check-lib-depends can either scan files from a built port after the fake stage from the WRKINST directory, or look directly inside a package.
...
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)) .
...
MK.CONF(5) - File Formats Manual # MK.CONF(5) - File Formats Manual
NAME # mk.conf - system-specific configuration parameters
SYNOPSIS # .include <bsd.own.mk>
DESCRIPTION # To get system-specific configuration parameters, <bsd.own.mk> will try to include the file specified by the MAKECONF variable. If MAKECONF is not set, or no such file exists, the system make configuration file /etc/mk.conf is included, if it exists. By default, this file does not exist, and must be created from scratch.
...
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).
...