wlandau
commented
3 months ago In the build details, it sounds like the r-universe packages.json file is updated automatically. This part feels familiar to me, but I'm wondering how this affects the build policy. Are all packages built together as well?
Yes, R-multiverse takes https://github.com/r-multiverse/contributions/tree/main/packages as input and then automatically generates packages.json. R-universe takes packages.json as input and then runs individual package-specific actions at https://github.com/r-universe/r-multiverse/actions. I believe these package-specific actions are triggered when new versions (in our case, releases) are created. I think https://github.com/r-universe-org/help/issues/369 is going to super important for both production and https://github.com/r-universe-org/help/issues/149.
How does this account for dependencies not available in the multiverse (notably from CRAN)? Assuming all packages get re-built at the same time, I assume there's a CRAN snapshot that corresponds to the multiverse release?
Right now, we are recommending that users set repos = c("https://r-multiverse.r-universe.dev", getOption("repos")) in install.packages(). During package checks, R-universe automatically pulls non-universe dependencies from CRAN.
In the current prototype phase, we are catering to packages not already on CRAN. But we hope to eventually scale up to a point where dependencies are also in-universe.
Hi Multiversers! Thanks for the discussion today!
I just wanted to reach out with a few immediate questions when reading through the multiverse.
packages.jsonfile is updated automatically. This part feels familiar to me, but I'm wondering how this affects the build policy. Are all packages built together as well?