-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update tex packages needed for knitting Rmd files to PDF #721
Conversation
If I create a new Rmarkdown file and try to knit to PDF, it has to install a big bunch of packages (which sometimes seems to take minutes, at least on my laptop) before it can actually knit. And this seems to happen each time the container starts. My guess is that the list of tex packages needed for rmd -> pdf knitting to work has just increased over time. I've added all the packages that were manually installed, by just looking at the 'render' tab in RStudio as installation was happening, and adding them. They are sorted alphabetically. I've removed any packages here that were also present in `install_jupyter.sh` to avoid duplication.
5081efe
to
96663a7
Compare
nice, this list looks good to me! |
Could you explain why you want avoiding duplication? |
@eitsupi I've removed the changes to |
cb6c498
to
d545333
Compare
@eitsupi the build failure now just looks like an intermittent network issue. Once this is merged, would you be so kind as to trigger a rebuild? Thanks. |
Could you update the NEWS? |
@eitsupi done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Thanks for the quick review, @eitsupi |
@yuvipanda #722 created #723 and #723 triggered a build, I think. |
- Brings us to latest point release of R - Brings in rocker-org/rocker-versioned2#721 Ref 2i2c-org/infrastructure#3178
Follow-up to rocker-org#721, adding tlmgr packages that *quarto* seems to need to knit to PDF. Without these, it takes a minute or more (depending on network) for first knit to happen apparently. Reported to me by users from University of Toronto
Follow-up to #721, adding tlmgr packages that *quarto* seems to need to knit to PDF. Without these, it takes a minute or more (depending on network) for first knit to happen apparently. Reported to me by users from University of Toronto
If I create a new Rmarkdown file and try to knit to PDF, it has to install a big bunch of packages (which sometimes seems to take minutes, at least on my laptop) before it can actually knit. And this seems to happen each time the container starts.
My guess is that the list of tex packages needed for rmd -> pdf knitting to work has just increased over time.
I've added all the packages that were manually installed, by just looking at the 'render' tab in RStudio as installation was happening, and adding them. They are sorted alphabetically.
I've removed any packages here that were also present in
install_jupyter.sh
to avoid duplication.Output from render tab indicating the packages that were being installed