more robust error handling for install2.r #50
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
install2.r has long had the option
-e
or--error
to make the script throw an error instead of the default behavior of a waring ifinstall.packages
fails to successfully install the package. Unfortunately, since R 3.4.0,utils
has started throwing a warning if the target repo does not have aPACKAGES.rds
insrc/contrib
. Many drat repositories just buildsrc/contrib/PACKAGES
andsrc/contrib/PACKAGES.gz
, so this means that the install2.r script now fails to install from drat repos (which is very sad, because drat repos are great).This patch provides a more robust approach to error when a package fails to install, but not simply error on any possible warning (as it does currently). This involves no change to the user interface of install2.r