program/tool from "FOO" to "TOOL_FOO". The new variables are:
TOOL_ASN1_COMPILE TOOL_CAP_MKDB TOOL_CAT TOOL_CKSUM TOOL_COMPILE_ET
TOOL_CONFIG TOOL_CRUNCHGEN TOOL_CTAGS TOOL_DB TOOL_EQN TOOL_FGEN
TOOL_GENCAT TOOL_GROFF TOOL_HEXDUMP TOOL_INDXBIB TOOL_INSTALLBOOT
TOOL_INSTALL_INFO TOOL_M4 TOOL_MAKEFS TOOL_MAKEINFO TOOL_MAKEWHATIS
TOOL_MDSETIMAGE TOOL_MENUC TOOL_MKCSMAPPER TOOL_MKESDB
TOOL_MKLOCALE TOOL_MKMAGIC TOOL_MKTEMP TOOL_MSGC TOOL_MTREE
TOOL_PAX TOOL_PIC TOOL_PREPMKBOOTIMAGE TOOL_PWD_MKDB TOOL_REFER
TOOL_ROFF_ASCII TOOL_ROFF_DVI TOOL_ROFF_HTML TOOL_ROFF_PS
TOOL_ROFF_RAW TOOL_RPCGEN TOOL_SOELIM TOOL_SUNLABEL TOOL_TBL
TOOL_UUDECODE TOOL_VGRIND TOOL_ZIC
For each, provide default in <bsd.sys.mk> of the form:
TOOL_FOO?= foo
and for the ${USETOOLS}=="yes" case in <bsd.own.mk>, provide override:
TOOL_FOO= ${TOOLDIR}/bin/${_TOOL_PREFIX}foo
Document all of these in bsd.README.
This cleans up a chunk of potential (and actual) namespace collision
within our build infrastructure, as well as improves consistency in
the share/mk documentation and provision of appropriate defaults for
each of these variables.
- Don't inherit altanative chracter set pairs.
- Define own (old xterm one) start/end alternative character set.
Problem reported along PR misc/20879 by Tsuburaya Kazuhito
<kazuhito_tsuburaya at hotmail.com> and supplied fix was applied.
PR misc/12400 by Kazu Yamamoto was for NetBSD 1.5 and currently it should
be simply 'xterm', noted by him.
This should fix problem less(1) with TERM=kterm and really close PR
misc/12400.
once in response to PR misc/3250 a while back and then re-appeared in the
broken form again!), and add `@8' and `k9' entries to irix-ansi-ap.
Fix prompted by Thomas Dickey, who originally spotted the issue in the
stripped-down termcap used by the sgimips install media.
PR: misc/17620.
Aymeric Vincent.
While we are here, remove local changes from the xterm-xf86-v32,
xterm-xf86-v33 and xterm-xf86-v333 entries and create our own xterm
and xterm-vb entries. Try to be compatible with as many xterm
implementations as possible.
- keep the case consistent between the actual name and what's referenced.
e.g, if it's `foo', don't use '.Nm Foo' at the start of a sentence.
- remove unnecessary `.Nm foo' after the first occurrence (except for
using `.Nm ""' if there's stuff following, or for the 2nd and so on
occurrences in a SYNOPSIS
- use Sx, Ic, Li, Em, Sq, and Xr as appropriate
lukem