-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
system dependencies request for multiple R packages #90
Comments
See r-lib/pak#327, which shows the API is actually already supporting this via multiple instances of the |
I am a bit surprised that people are surprised that this is working. I have been using the following code for a bit, basically putting together a fake, single-line url <- glue::glue(
"https://packagemanager.rstudio.com/__api__/repos/1/sysreqs?",
"distribution={distribution}&release={release}&suggests={suggests}"
)
body <- paste("Imports:", paste(packages, collapse = ", "))
res <- httr::content(httr::POST(url, body = body)) This may be obsolete now that multiple |
@bersbersbers, multiple It is in any case good to have both approaches tracked in this issue for the posterity and the community! |
Hey, sorry for missing this before, but I can confirm that the I believe the To make this less confusing, we could add some pointers to the API documentation in the README for this repo, and maybe even some example API requests. |
It would be great if the system requirements for multiple R packages could be requested in one call. I have created a related issue with example code on r-lib/remotes#650 where I was pointed to this project.
Here are my use cases. Assuming we start from a vanilla OS with R installed and I would like to setup an R environment with the packages
png
,gh
,ggplot2
,credentials
,gitcreds
,showimage
,gert
, andsystemfonts
installed. I would like to have the list of all system requirements givenrecursive
argument) and haveinstall.packages
take care at run-time of the system requirements:Note those two use cases are very similar and 2. is enough from a API to get to 1.
The text was updated successfully, but these errors were encountered: