Closed k-doering-NOAA closed 6 months ago
We use it for our time-series packages: https://atsa-es.r-universe.dev/packages. So easy to set up and makes it much much easier for people to install your GitHub packages esp if they include C++ code (e.g. TMB) because they don't have to build them. Works like installing from CRAN.
We do have this experimental FIT one.
I think the other advantages is you need the whole r-tools chain for github pkgs with c++ code if you install from r universe.
I attended a R open sci coworking session with Jereon Ooms, the creator and developer of the R universe. Here's some things I learned:
branch
and subdir
fields that can be included in the package.json file. I'm struggling to find documentation, but the subdir
allows you to specify a subdirectory that the R package is in, and the branch
field allows you to specify a branch or tag that the binary should be built from. Pattern matching also works: for example, you could use *release
I think builds any release created on GitHub?Recent value added: devtools::install_github() isn't working on NOAA laptops, and pak::pak() required the package build tool chain. Installation from R universe does not, so the user was able to install from R universe as a "quick fix" way to get the package nmfspalette, which is not on CRAN.
R universe can be a helpful tool for users and developers of the toolbox; We could provide instructions on how to install using R universe on the R package pages?
I think there are some clear uses of R universe that could be helpful. I think when developing the FY25 plan, we can consider specific action items based on what we know about R universe. For example:
Some information about how other communities are using R universe