ports/build-tools/byacc/pkg.conf

pkg_name="byacc"
pkg_license="bsd-2-clause"
pkg_ver="git"
# %yacc, low pref: the default yacc provider -- needs nothing but a C
# compiler (no autoconf/automake/libtool/gettext/gperf/texinfo/help2man
# chain gnu-bison's own build pulls in), and every current %yacc
# consumer in this tree (verified directly against each one's own
# grammar file, not assumed) uses no real bison-specific extension.
# gnu-bison itself stays the higher-pref, opt-in alternative for
# whatever genuinely needs one (real %define/%parse-param/%lex-param
# directives, or a CMake find_package(BISON REQUIRED) version check) --
# see its own pkg.conf comment. NOT pkg_conflicts="gnu-bison" (was,
# until this was hit for real): something can depend on gnu-bison
# DIRECTLY, for its own "bison" binary specifically, independent of
# whichever %yacc provider a given site pins (sysutils/gnu-patch's own
# hard dependency is exactly this case) -- gnu-bison's own add.sh now
# configures with --disable-yacc precisely so it never installs
# anything that would collide with byacc's own "yacc"/"yacc.1" in the
# first place, so the two coexist with no real conflict left at all.
pkg_tags="yacc"
pkg_pref="15"
# %awk: byacc's own ./configure (autoconf's stock AC_PROG_AWK check)
# needs SOME awk present at configure time -- hit for real, "No awk
# program found" installing byacc with literally nothing satisfying
# %awk yet. NOT circular despite gawk itself depending on %yacc (this
# port): build-tools/onetrueawk (the lower-pref, default %awk
# provider) has no %yacc dependency of its own at all, so this
# resolves through onetrueawk without ever looping back through byacc
# again -- only an explicit, deliberate "gawk is the only %awk
# provider around" scenario could cycle, and mp's own resolver already
# prefers the lower-pref (onetrueawk) provider first regardless.
pkg_deps="%awk"