Gábor Csárdi

We are already installing tinytex on some containers. IDK if all containers should have it, you don't need to build the vignettes to run an asan or valgrind check. AFAIR...

`processx::process` does not use `system`. More importantly the IPC in processx is a Unix socket (or a Windows named pipe), so it is not going to work across machines.

Some of cli is still in flux, so it is bit early to create a cheat sheet now. But maybe we can improve the organization of the existing docs at...

I think this is a circular dependency between DPchecker and EMLeditor. The error message should be better, though.

Yes, ideally it would be a better error message, but it is possible to install packages with circular dependencies in R, so this is not going to work, possibly ever.

You cannot use pak to install itself. If you want to install the dev version, you can install a nightly build from https://pak.r-lib.org/reference/install.html#nightly-builds

This container has ``` > getOption("repos") CRAN "https://p3m.dev/cran/__linux__/jammy/latest" ``` so there are no source packages available. You need to add another repo that has source packages.

I _think_ changing the cert path with the option does not work because the pak subprocess does not read the profile, so it does not see the option. Two possible...

You can install pak manually, delete the cert file, and use `pak-version: none`.

> I have not been able to properly set `R_LIB_FOR_PAK` Why not? You can set it to whatever you like, just install pak there.