-
-
Notifications
You must be signed in to change notification settings - Fork 4
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
Dependencies of non-available packages #14
Comments
I think one of the strengths of the current design is that it does not reinvent RSPM appears to fall back to 'compiling from source' for binaries it does not have, which is twice as bad because presumably it does not have them for lack of easy building so by then calling for a build from source it sets it up for a fail in all cases I encountered so far (in Docker settings). |
I think current behaviour is ok, but I'm probably too biased because I programmed it. Above I was specifically thinking about something like I was considering (3) if your expectations differed a bit and (2) or (4) only if they differed a lot with my (probably biased) expectations. But if not, it's ok as it is. |
Suppose that a user wants to
install.packages(c("pkgA", "pkgB"))
(withbspm
enabled). Suppose thatpkgA
is provided in the system repos and has zero dependencies;pkgB
is not provided in the system repos and depends onpkgC
, which is available in the system repos. @eddelbuettel what would you expect?pkgA
is installed from system repos.pkgB
andpkgC
are installed from CRAN (current behaviour).pkgA
andpkgC
are installed from system repos.pkgB
is installed from CRAN.options
.options
.The text was updated successfully, but these errors were encountered: