ports/ssl/libressl/pkg.conf

pkg_name="libressl"
pkg_license="isc"
pkg_ver="git"
pkg_tags="ssl"
pkg_pref="10"
pkg_conflicts="openssl"
# %patch: libressl's own upstream autogen.sh (via update.sh) applies
# its bundled patches/*.patch files with a bare "patch -p0", relying on
# whatever "patch" happens to be on PATH -- busybox's own patch applet
# is what silently answers that on a base system with no real GNU
# patch installed, and it doesn't handle every hunk GNU patch does
# (hit for real: a fuzzy-context hunk against crypto/bn/arch/aarch64/
# bn_arch.h failed outright under busybox's patch), NOR does it appear
# to propagate that failure as a nonzero exit the way update.sh's own
# "set -e" expects -- the script kept going with a half-patched tree
# instead of stopping, so the real failure only surfaced later ("./
# configure: not found") once autogen.sh already thought it succeeded.
pkg_deps="gnu-autoconf gnu-automake gnu-libtool %patch"
 
# "mp reinstall --inplace" builds into a throwaway, ephemeral prefix and
# merges the result onto the live root afterward -- fine for most
# ports, but libressl bakes its build-time --prefix into MULTIPLE
# artifacts, not just one: libtool's own .la files (dependency_libs=
# and friends, needed by anything else that links against libcrypto/
# libssl/libtls via libtool -- hit for real: networking/curl's own
# build failed with "'/usr/mp/.inplace/libressl/root/lib/libcrypto.la'
# is not a valid libtool archive" once that ephemeral scratch dir was
# cleaned up) AND its own openssl(1) CLI's compiled-in default config
# path (a "can't open config file" warning against the same dead
# ephemeral path). mpx's own merge command only rewrites symlink
# targets rooted at the source prefix, not arbitrary text embedded
# inside a file, so neither of these gets fixed up the way an
# --inplace-built symlink already would be. same class of incident as
# languages/perl5 and build-tools/gnu-{autoconf,automake,libtool}'s own
# identical pkg_no_inplace.
pkg_no_inplace="yes"