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) .
...
CABAL-MODULE(5) - File Formats Manual # CABAL-MODULE(5) - File Formats Manual
NAME # cabal-module - devel/cabal port module for building Haskell programs
DESCRIPTION # This manual page documents the behavior of setting MODULES=devel/cabal in the ports(7) tree.
Uses cabal(1) to automate packaging Haskell binary projects. During fetch, the dependent packages enumerated in MODCABAL_MANIFEST are downloaded into the hackage subdirectory of DIST_SUBDIR. During post-extract, the dependency sources are unpacked into WORKDIR.
...
CARGO-MODULE(5) - File Formats Manual # CARGO-MODULE(5) - File Formats Manual
NAME # cargo-module - devel/cargo port module
DESCRIPTION # This manual page documents the behavior of setting MODULES=devel/cargo in the ports(7) tree.
Automates download and compilation of dependencies of a Rust project using cargo(1).
During fetch, static dependencies (“crates”) listed in MODCARGO_CRATES are downloaded using MODCARGO_DIST_SUBDIR as DIST_SUBDIR.
During post-extract, crates defined in MODCARGO_CRATES are moved to the MODCARGO_VENDOR_DIR directory.
...
GNOME-MODULE(5) - File Formats Manual # GNOME-MODULE(5) - File Formats Manual
NAME # gnome-module - x11/gnome port module
DESCRIPTION # This manual page documents the behavior of setting MODULES=x11/gnome in the ports(7) tree.
This module has full support for the gnu, simple, meson and cmake CONFIGURE_STYLE.
If DIST_TUPLE is set and the gnome template is used, this module will set default values for GNOME_PROJECT, GNOME_VERSION, WRKDIST, and EXTRACT_SUFX.
If both GNOME_PROJECT and GNOME_VERSION are set, this module defines DISTNAME, MASTER_SITES, adds x11/gnome to CATEGORIES and EXTRACT_SUFX will default to .
...
GO-MODULE(5) - File Formats Manual # GO-MODULE(5) - File Formats Manual
NAME # go-module - lang/go port module
DESCRIPTION # This manual page documents the behavior of setting MODULES=lang/go in the ports(7) tree.
Adds Go toolchain support. Requires ALL_TARGET to be set to canonical Go import path of port. (Module sets it automatically for ports that use GH_ACCOUNT and GH_PROJECT macros.)
During execution of pre-configure target module moves source code from ${MODGO_SUBDIR} to ${WRKSRC}, subdirectory of ${MODGO_WORKSPACE} - specially-crafted Go workspace located at ${WRKDIR}/go.
...
PORTGEN(1) - General Commands Manual # PORTGEN(1) - General Commands Manual
NAME # portgen - port modules on the fly
SYNOPSIS # portgen [-m makeopt] type module-name
DESCRIPTION # The portgen utility creates ports for the given module-name from type module framework. The module is downloaded, analyzed and translated into a port. Any missing dependencies are handled recursively. New ports will land under ${PORTSDIR}/mystuff. The PORTSDIR value will be taken from current user environment, and defaults to /usr/ports.
...
PORTS(7) - Miscellaneous Information Manual # PORTS(7) - Miscellaneous Information Manual
NAME # ports - contributed applications
DESCRIPTION # The OpenBSD Ports Collection is the infrastructure used to create binary packages for third party applications.
For normal usage refer to packages(7), as most ports produce binary packages which are available from the official HTTP mirrors.
Each port contains any patches necessary to make the original application source code compile and run on OpenBSD.
...
PYTHON-MODULE(5) - File Formats Manual # PYTHON-MODULE(5) - File Formats Manual
NAME # python-module - lang/python port module
DESCRIPTION # This manual page documents the behavior of setting MODULES=lang/python in the ports(7) tree.
By default, the module sets MODPY_VERSION to the appropriate python version (depending on the existence/presence of a ‘python3’ FLAVOR) , but MODPY_VERSION may be set manually to ${MODPY_DEFAULT_VERSION_2} for legacy ports.
The module then sets MODPY_BIN, MODPY_INCDIR, MODPY_LIBDIR, MODPY_SITEPKG, MODPY_SETUP, MODPY_TEST_DIR, MODPY_TEST_LOCALE, MODPY_WANTLIB, MODPY_LIB_DEPENDS, MODPY_RUN_DEPENDS, MODPY_TEST_DEPENDS, MODPY_BUILD_DEPENDS, and MODPY_ADJ_FILES accordingly.
...
QMAKE-MODULE(5) - File Formats Manual # QMAKE-MODULE(5) - File Formats Manual
NAME # qmake-module - devel/qmake port module
DESCRIPTION # This manual page documents the behavior of setting MODULES=devel/qmake in the ports(7) tree.
This module automates usage of qmake, independently of the actual version of Qt being used. This module requires that one of the x11/qt*‌ to be used as well.
If CONFIGURE_STYLE was not set before, sets its value to ‘qmake’.
...
RUBY-MODULE(5) - File Formats Manual # RUBY-MODULE(5) - File Formats Manual
NAME # ruby-module - lang/ruby port module
DESCRIPTION # This manual page documents the behavior of setting MODULES``=lang/ruby in the ports(7) tree.
The main usage of the lang/ruby module is to allow a single Ruby gem-based port to build packages for multiple versions of Ruby. The lang/ruby module also simplifies ports that depend on Ruby by automatically setting up the correct dependencies and defining commonly needed variables.
...