ports/build-tools/onetrueawk/del.sh

set -e
 
# see e.g. compilers/gcc's or networking/curl's own identical guard/
# comment this same pass: remove: can run with no checkout present at
# all (before add.sh ever (re-)clones one on a reinstall, or after "mp
# clean onetrueawk" wipes a stale one) -- but unlike a normal autotools
# port, this one never had a "make uninstall" to run anyway (see
# add.sh's own comment on why install: is a manual "install" call
# instead), so remove: is just the manual mirror of that: delete
# exactly the two files add.sh put down. safe to run unconditionally,
# checkout present or not -- mp's own manifest sweep covers this
# regardless, this is just the explicit/fast path.
# if textproc/gawk is also installed, don't touch bin/awk at all --
# gawk's own USE=own_awk_symlink (see its own add.sh) can make IT the
# real owner of that exact path, and onetrueawk's own manifest has no
# way to know its ownership was superseded after the fact (mp's own
# manifest tracking doesn't follow a path's ownership across packages
# when a LATER install legitimately overwrites an EARLIER one's file --
# confirmed the hard way: removing onetrueawk here destroyed gawk's
# own freshly-claimed "awk", not just onetrueawk's original one).
# checking for /usr/bin/gawk specifically (not a USE flag -- gawk's
# own USE=own_awk_symlink isn't visible from here, this is a different
# package's own phase script) is a deliberately conservative signal:
# a stray, orphaned bin/awk left behind on removal when gawk ISN'T the
# one owning it (own_awk_symlink off, gawk kept purely as some other
# port's own named dependency) is a minor, harmless leftover mp's own
# manifest sweep still cleans up regardless -- destroying a file
# something else actually needs is not nearly as recoverable a mistake.
if [ ! -f $MP_PREFIX/bin/gawk ]; then
	rm -f $MP_PREFIX/bin/awk
fi
rm -f $MP_PREFIX/share/man/man1/awk.1
rm -rf onetrueawk