Pomtex::Engine::RuntimeGuard
Constants
No map entry and no PK bitmap: pdfTeX gave up on the font entirely.
Constructors
Class methods
The first error and its context, for display after a failed run.
The command in the user's sources that asked for the font. The log can't tell: fontspec loads fonts at \begin{document}.
Extracts everything the log says is missing. Exposed for testing.
Instance methods
Compiles runner's document. Returns the final result (successful or not).
The whole compile holds a shared cache lock, so pomtex clean in another
terminal cannot remove files mid-build; fetches upgrade it to exclusive.
fontspec selects fonts by family name, which can differ from the file name pomtex resolved: "Inconsolata" lives in Inconsolatazi4-Regular.otf, whose family is "Inconsolatazi4". Name the families that do exist.
Roots are known missing; dependencies are probed by kpathsea, layer by layer.
Provisions what the document asks for, then follows the load graph through
the arils pomtex planted: their own \RequirePackage, \input, \tcbuselibrary,
... are fetched in batches before the first engine run. TeX Live's dependency
metadata misses these (e.g. tcolorbox's skins library needs tikzfill), and
with -halt-on-error each one would otherwise cost a full compile.
Only aril files are scanned: the rind and system TeX ship complete dependency sets, and following their conditional loads would over-fetch.
Makes files (and fonts) visible to kpathsea, fetching arils for whatever
is missing. Returns the number of arils planted.
Finds a helper program such as biber, planting its binary aril if needed. With the rind, a biber from $PATH is not trusted: biber must match the biblatex version, and the planted one comes from the same TeX Live release.