Re: xdvipdfmx:fatal: Unable to find TFM file "latt1095".

[Dan Eble]

On Nov 23, 2020, at 05:17, Werner LEMBERG <wl@gnu.org> wrote:
> I think you either don't use TeX a lot, or your use-cases are very
> restricted.  As soon as I update TeXLive, I have to regenerate the
> format files by `fmtutil-user`, which are all stored in $HOME.
> Similarly, I have to regenerate various `.map` files by calling
> `updmap-user` to integrate my private fonts into TeX.  Even for direct
> LilyPond work I need some local files: To view the `fetaXXX.dvi` proof
> sheet files the bitmap font `black.600pk` and its metric file
> `black.tfm` must be generated.
> 
>> And for that reason, I think that building LilyPond on a fresh
>> system should leave nothing behind after purging the build tree.
> 
> I strongly disagree.  It's definitely not LilyPond's job to decide
> where the TeX system stores its internal files.  In other words, the
> build infracture has to adjust this, to be handled outside of
> LilyPond.

Should this part of the font setup be baked into the Docker image?
— 
Dan