ports/build-tools/onetrueawk/pkg.conf

pkg_name="onetrueawk"
pkg_license="bsd-3-clause"
pkg_ver="git"
# %awk, low pref (below gawk's own pkg_pref="30", see gawk's own
# pkg.conf): the default awk provider. verified safe, not assumed --
# tested byte-for-byte against the real script (rsync's own
# help-from-md.awk, generating rsync.1's own built-in help text) that
# originally justified pinning AWK=gawk elsewhere in this tree: 157/157
# lines identical to gawk's own output. gawk's grammar itself (awkgram.y,
# checked directly) also uses zero bison-specific directives, so nothing
# here needs gawk's own heavier gnu-bison/gnu-autoconf/gnu-automake/
# gnu-libtool/gnu-gettext dependency chain just to have a working awk.
# real, confirmed bug this fixes: busybox's own "awk" applet has a
# genuine gsub() escaping bug (gsub(/"/, "\\\"") silently drops the
# escape instead of inserting it) that gawk's own "AWK=gawk" workarounds
# elsewhere in this tree exist specifically because of -- but busybox's
# own applet currently still wins any BARE "awk" invocation on $PATH
# ordering (/usr/bin before /bin) whenever gawk isn't explicitly named,
# same class of incident as busybox's own passwd/chpasswd/nologin
# shadowing fixed earlier (see busybox's own pkg.conf/add.sh).
#
# NOT pkg_conflicts="gawk": "awk" is a real path collision with gawk's
# own installed "awk" binary ONLY when gawk's own USE_own_awk_symlink
# is turned on (off by default) -- see gawk's own pkg.conf for the
# full story. the common case (gawk installed as some OTHER port's own
# specific, named dependency, e.g. compilers/gcc's real need for it)
# doesn't collide at all, and a blanket conflict here would incorrectly
# forbid exactly that. mp's own generic file-conflict detector is the
# correct, precise safety net for the one remaining real collision case.
pkg_tags="awk"
pkg_pref="15"
pkg_deps=""
 
# mplib::resolve::clean_manifest_files runs independently of del.sh --
# it deletes every file in a package's OWN tracked manifest as part of
# a reinstall/remove, regardless of what del.sh itself does or doesn't
# do, and has zero awareness that a path it's about to sweep might have
# been legitimately taken over by a DIFFERENT package since this one's
# own manifest was last written. confirmed the hard way, again: even
# with del.sh's own "don't touch bin/awk if gawk owns it now" guard in
# place, removing onetrueawk STILL destroyed gawk's own freshly-claimed
# "awk" (own_awk_symlink on) -- "manifest cleanup removed 1 leftover
# file(s)" bypassing that guard entirely, the exact same class of
# incident [[gcc_musl_bootstrap_lessons]] already documents for gcc's
# own 1847 files. same fix: pkg_manifest_cleanup="no" turns this sweep
# off, leaving del.sh's own explicit (and already ownership-aware)
# logic as the only thing that ever touches these paths on removal.
pkg_manifest_cleanup="no"