| Age | Commit message (Collapse) | Author |
|---|
|
In this way, files of different types can easily be combined, as
long as a common format to to through can be specified.
|
|
... in order to allow a specialized typesetting image to be used,
so that the (potentially large) typesetting dependencies do not
have to be installed in the normal build images.
|
|
In this way, meta data can be provided that is not statically
known, but has to be computed via an action.
|
|
... and the BLOB construct instead of echo.
The echo(1) function is usually shell built in. This in itself
is a reasonalbe design decission, as there is no need to start
an external program just to join a couple of strings by spaces.
Unfortunately, however, shells don't agree on the semantics of
echo, in particular about what the correct invocation is to
output a literal backslash; this can be seen from the following
invovations.
~>dash -c 'echo '\''\\'\'''
\
~>bash -c 'echo '\''\\'\'''
\\
~>
Now, both of those shells can act as the, supposedly POSIX-compliant
sh. Work around these incompatibilities by generating BLOBs for
the \begin/\end{verbatim} literal and join them with cat(1).
|
|
...the main improvement wrt to standalone rule is the usage of
latexmk, which automatically runs latex the right number of times,
and, if needed, can call bibtex as well.
Co-authored-by: Oliver Reiche <oliver.reiche@huawei.com>
|
|
|
|
The rules are still very basic; in particular, the latex rules do not
support bibtex. Nevertheless, having typesetting rules in that basic
form is already useful, especially when creating documents (slides,
handbooks, web pages, etc) containing generated files, like sample
logs of tools under development.
Co-authored-by: Oliver Reiche <oliver.reiche@huawei.com>
|
