Changes since 2020-01-19:
2020-04-12:
- added cross realm support
- added AggregateError and Promise.any
- added env, uid and gid options in os.exec()
- misc bug fixes
2020-03-16:
- reworked error handling in std and os libraries: suppressed I/O
exceptions in std FILE functions and return a positive errno value
when it is explicit
- output exception messages to stderr
- added std.loadFile(), std.strerror(), std.FILE.prototype.tello()
- added JS_GetRuntimeOpaque(), JS_SetRuntimeOpaque(), JS_NewUint32()
- updated to Unicode 13.0.0
- misc bug fixes
The package-specific options.mk is included by djbware.mk and must
therefore not be included by the package Makefile itself. This fixes the
PKG_SUPPORTED_OPTIONS displayed by show-options.
Found by making the package-settable variables in mk/bsd.options.mk
read-only.
Packages that don't declare USE_TOOLS+=perl and whose configure script
invokes perl produce a warning.
Usually warnings are ignored, but they can also be configured as errors,
for example during a strict bulk build. In this situation it is
necessary to override the default behavior of the perl tool to fail
silently. Up to now, defining both TOOLS_BROKEN+=perl and
TOOLS_FAIL+=perl produced a duplicate make target.
To handle this situation, let TOOLS_BROKEN+=perl take precedence over
TOOLS_FAIL+=perl. This is much easier than finding out in each case how
to disable the perl check in the configure script, which is most often
done by adding any of the following to CONFIGURE_ENV: PERL=#none,
ac_cv_prog_PERL=#none, ac_cv_path_PERL=#none.
General:
* The \input primitive in all TeX engines, including tex, now also accepts a
group-delimited filename argument, as a system-dependent extension. The usage
with a standard space/token-delimited filename is completely unchanged. The
group-delimited argument was previously implemented in LuaTeX; now it is available
in all engines. ASCII double quote characters (") are removed from the filename,
but it is otherwise left unchanged after tokenization. This does not currently
affect LaTeX’s \input command, as that is a macro redefinition of the standard
\input primitive.
* New option –cnf-line for kpsewhich, tex, mf, and all other engines, to support
arbitrary configuration settings on the command line.
* The addition of various primitives to various engines in this and previous years
is intended to result in a common set of functionality available across
all engines.
epTeX, eupTeX: New primitives \Uchar, \Ucharcat, \current(x)spacingmode, \ifincsname;
revise \fontchar?? and \iffontchar. For eupTeX only: \currentcjktoken.
LuaTeX: Integration with HarfBuzz library, available as new engines luahbtex
(used for lualatex) and luajithbtex. New primitives: \eTeXgluestretchorder,
\eTeXglueshrinkorder.
pdfTeX: New primitive \pdfmajorversion; this merely changes the version number
in the PDF output; it has no effect on any PDF content. \pdfximage and similar
now search for image files in the same way as \openin.
pTeX: New primitives \ifjfont, \iftfont. Also in epTeX, upTeX, eupTeX.
XeTeX: Fixes for \Umathchardef, \XeTeXinterchartoks, \pdfsavepos.
Dvips: Output encodings for bitmap fonts, for better copy/paste capabilities.
Changelog:
Fixed
Fixed a bug causing some add-ons such as Amazon Assistant to see multiple
onConnect events, impairing functionality (bug 1635637)
Fixed a crash on 32-bit Windows systems with some nVidia drivers
installed (bug 1635823)
This information is useful for getting the variable name that corresponds
to a tool. In most cases this is just the uppercase name of the tool,
but there are exceptions like ${SETENV} for env, ${HOSTNAME_CMD} for
hostname.
It looks wrong that the paths in constants.py depend on the operating
system, but that's not caused by the latest SUBST changes, so I'm leaving
that as-is. Someone familiar with this package should have a look.
