Gábor Csárdi

I guess the second pak call is trying to update a package that was installed in the first pak call.

I am going to try to fix this now. A small reprex `Dockerfile`: ``` FROM rhub/r-minimal WORKDIR /root RUN installr -c -p RUN Rscript -e 'pak::pkg_install("rlang")' RUN Rscript -e 'pak::pkg_install("r-lib/rlang")'...

OK, this is now fixed in pkgdepends, and the nightly `devel` Linux builds of pak. So this works now: ``` FROM rhub/r-minimal WORKDIR /root RUN installr -c RUN Rscript -e...

The issue is that it is not always easy to decide if a compiler is needed or not. Not all source packages need a compiler. In practice all downloaded packages...

Most of the time, yes. But e.g. for packages on GH, no, unless the maintainer manually adds it.

I am sorry for the slow response. Do you still have this issue?

How did you install pak? Can you try the devel version? You can install it like this: ```r install.packages("pak", repos = "https://r-lib.github.io/p/pak/devel") ``` Also, what's the output of ```r getOption("repos")...

Can you please try a simple source package? ``` pak::pkg_install("pkgconfig?source") ``` Can you also try to run these? ``` system2(system.file(package = "pak", "library", "zip", "bin", "x64", "zip.exe"), "--help") system2(system.file(package =...

One more shot in the dark: ``` Sys.which("zip") Sys.which("unzip") ```

I am sorry, I have no clue what is going on. What is your exact OS? Do you have rtools40 installed?