Problems found locating distfiles:
Package colorls: missing distfile ls.tar.gz
Package molden: missing distfile molden-4.6/molden4.6.tar.gz
Package softmaker-office-demo: missing distfile ofl06trial.tgz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
load the DEC Special Graphics (VT line draw) characters into graphics set
GS0 -- with lock shift 0, aka LS0, aka SO, aka ^0 -- to then enable GS0.
Since GS0 is the default, the full procedure is really only necessary when
displaying line draw and alphanumeric characters on the same line. With the
last patch to enable line draw characters, ESC(0 was always taken to mean
ASCII SI (shift in), and ^0 was always taken to to mean SO (shift out),
so for programs that did the right thing (e.g. "pstree"), "dt" was simply
setting, then unsetting, the alternate character set attribute, causing
the desired line draw characters never to be displayed.
To deal with that, introduce a layer of abstraction, such that ESC(0
and friends now only set per-VT variables, rather than directly set the
attribute. Initialize these variables so that SO and SI, taken alone, will
do the expected thing, and extend the state machine so that a changed GS0
will become active at the next carriage return, or immediately if an LS0
was already seen on that line (all very much like a real VT).
Bump version to dt-1.1.7nb2.
the actual, display line width exceeds the size of the array allotted for
it, by increasing the size of said array to 224 characters. This is good to
about 1350 pixels horizontal with the small font, or nearly 1800 with the
large font.
- - Don't try to build on powerpc. This is not useful, and it was never
tested anyway.
- - ${IGNORE} doesn't need to be set from within a .BEGIN target.
- - Move lines that don't need to be after .include ../../bsd.prefs.mk
into the main body, same for lines that don't need to be in the header.
build a binary package with this definition would fail as the PLIST is
not correct.
If a package's documentation is overwhelming, it should arguably be handled
in a separate pre-requisite documentation package.
