Open kfeinauer opened 2 months ago
We should ask in the quarto Slack channel and can go from there
Guidance from Quarto: https://quarto.org/docs/output-formats/pdf-engine.html#managing-tex
We may want to implement this outside of quarto, but use the same underlying method to update tinytex.
In the base image, we install Tex here:
https://github.com/rstudio/rstudio-docker-products/blob/75f550bf7123c765712e23eae20df898a362b1ca/product/base/Dockerfile.ubuntu2204#L33-L39
This allows users to use Quarto and RMarkdown to knit documents, but this will only work for so long. Eventually, next calendar year, the default Tex repos will bump versions and no longer be compatible, as mentioned by a customer. This prevents rendering of any Quarto/RMarkdown documents unless worked around.
Example .qmd file content:
Error when rendering:
This can be mitigated by users by running a command to pin the Tex repos to an older version as mentioned in this thread but this is an annoyance to customers and either requires them to run this every time they do work, or to modify the image manually.
Ideally this error would never surface to customers and things would just work, falling back to older Tex repos if necessary. I do not think we should be rebuilding images with updated versions of Tex.
The Quarto team may have some ideas on how to tackle this issue.