what is the behavior of install.packages in case multiple repos are specified?

Question

It is not clear from the documentation what is the behavior if multiple repos are specified at install.packages. My intuition told me that it would try the first repo, and if the package is not found, it would try the second, and so on. Unfortunately it does not appear to be the case. What I see is that only the first is tried, and an error is returned (because the repo does not contain the package). There's also lack of clarity of how the "CRAN" entry is handled compared to a different entry.

What I want to have is a local CRAN with my own packages (specified first), and the global CRAN with the larger package sets (specified second), and be able to install from the local unless the package is not found (and in that case, it will fall back to the global)

Here is the error I get

> setRepositories(graphics = FALSE, ind=NULL, addURLs=c(ciccio="file:qs-cran", CRAN="https://mran.microsoft.com/snapshot/2018-08-01"))
> install.packages("zizzio")
Error in read.dcf(file = tmpf) : cannot open the connection
In addition: Warning messages:
1: package ‘zizzio’ is not available (for R version 3.5.3) 
2: In read.dcf(file = tmpf) :
  cannot open compressed file 'qs-cran/bin/macosx/el-capitan/contrib/3.5/PACKAGES', probable reason 'No such file or directory'
> install.packages("zizzio", type="source")
Warning message:
package ‘zizzio’ is not available (for R version 3.5.3)

I think it only does one. Try using `tryCatch` to install from the global if there is an error installing from the local. — Jonny Phelps, Oct 11 '19 at 12:46
@JonnyPhelps the problem is that if I do so, it would not download global dependencies required by my local one. — Stefano Borini, Oct 11 '19 at 12:56
Does `zizzio` have an entry in the `PACKAGES` file? If so, does its `Depends:` entry require a version of R above 3.5.3? — Nathan Werth, Oct 11 '19 at 13:49

score 0 · Answer 1 · answered Oct 11 '19 at 13:25

0

I think your problem is that your local repository doesn't have a PACKAGES file. Every directory in a repo that has packages must have this file, because it's how R knows what's available. So R tries that repo first, hits an error when the file it needs doesn't exist, and stops before looking at the next repo.

The official manual "R Installation and Administration" describes what's necessary for a repository.

You can create the PACKAGES file with:

tools::write_PACKAGES(
  "qs-cran/bin/macosx/el-capitan/contrib/3.5",
  type = "mac.binary"
)

Afterwards, your repository should look like this:

qs-cran/
└ bin/macosx/el-capitan/contrib/3.5/
    ├ PACKAGES
    └ zizzio_1.0.0.zip

From then on, anytime you add, change, or remove a package, use:

tools::update_PACKAGES(
  "qs-cran/bin/macosx/el-capitan/contrib/3.5",
  type = "mac.binary"
)

answered Oct 11 '19 at 13:25

Nathan Werth

5,093
18
25

the PACKAGES file is right there in /src/contrib/. I would expect that in absence of binary packages (I don't have any) it would try the source. I get the same result if I pass type="source" as indicated – Stefano Borini Oct 11 '19 at 13:27
On the topic, I created the local cran with miniCRAN – Stefano Borini Oct 11 '19 at 13:28
Because you didn't specify in `install.packages` that you wanted a source package, R also looked for binary packages. Probably in case the package you want were available as a binary but not as source. – Nathan Werth Oct 11 '19 at 13:35
I did. see my example. – Stefano Borini Oct 11 '19 at 13:35
Sorry for not noticing. Feel free to downvote my answer to flag it as irrelevant. – Nathan Werth Oct 11 '19 at 13:40

what is the behavior of install.packages in case multiple repos are specified?

1 Answers1

Linked