This is tricky:
R CMD INSTALL
has a --build
argument, but that puts the output
file in the current working directory, and we might overwrite something
there, so we don't want this.utils::install.packages
does not work us a lot in this
respect, because it only gives warnings for failed installs.--no-test-load
, and then the actual binary might be broken.downloaded_packages
.Even if we don't use --build
, but create the binary package archive
manually, we need to know which installs fails, because we don not want
to package up those.
So here is a plan:
--no-test-load
argument is included in INSTALL_opts
, then
we do not deal with binary packages at all. (Possibly, some other
arguments could be treated the same, e.g. --fake
.)utils::install.packages
. (We also
re-throw them.)lib
directory where the new packages were installed.install_packages
invocation, and these will be our candidates to package up.Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.