ports/build-tools/gnu-bison/pkg.conf

pkg_name="gnu-bison"
pkg_license="gpl-3.0+"
pkg_ver="git"
# %yacc: gnu-bison's own upstream build can install a "yacc" POSIX-
# compat wrapper script alongside "bison" itself, a real path
# collision with build-tools/byacc's own "yacc" binary. pkg_pref="45"
# (higher/heavier than byacc's own "15") already makes byacc the
# %yacc tag's default pick, same ncurses/gnu-ncurses and curl/curl-
# full shape: the lighter alternative default, this one opt-in for
# whatever genuinely needs real bison-only extensions (%define/
# %parse-param/%lex-param directives, or a CMake find_package(BISON
# REQUIRED) version check that only a binary literally named "bison"
# satisfies).
#
# yacc_wrapper (bare, off by default): whether to also build/install
# that "yacc" wrapper (add.sh's own --enable-yacc/--disable-yacc, a
# real upstream configure.ac switch). OFF by default so gnu-bison
# never collides with byacc's own "yacc" the moment something needs
# gnu-bison DIRECTLY (sysutils/gnu-patch's own hard dependency, for
# the "bison" binary specifically -- confirmed for real: mp's
# CONFLICT_PRIORITY can only let the package currently installing WIN
# a colliding file outright, never "install everything except this one
# path", so avoiding the collision at the source beats fighting over
# ownership of it after the fact). a site with no byacc installed (or
# that genuinely wants gnu-bison's own wrapper as the live "yacc")
# opts in with "gnu-bison: USE=yacc_wrapper".
pkg_tags="yacc"
pkg_pref="45"
pkg_use="yacc_wrapper"
pkg_deps="gnu-m4 gnu-autoconf gnu-automake gnu-libtool gnu-gettext gperf gnu-texinfo help2man gmake flex"