...instead of devtools::install, which insists in checking for updates to all dependencies every call, even when upgrade = FALSE.
Across all packages this adds up to a lot of repeated checks, and in combination with our separate dependency check it's enough to exceed GitHub APi request rate limits during CI builds.
remotes::install_local appears to not check dependencies at all when dependencies=FALSE, which is what we want for this case.
(Side note: The force=TRUE is needed to make sure Make reinstalls your changes during local development, because install_local defaults to not installing the package if its "SHA has not changed"... but for local packages it treats the package version string as the "SHA" and doesn't notice edits that don't change the version.)
Description
Motivation and Context
Review Time Estimate
[ ] Immediately
[ ] Within one week
[ ] When possible
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[ ] My change requires a change to the documentation.
...instead of devtools::install, which insists in checking for updates to all dependencies every call, even when
upgrade = FALSE. Across all packages this adds up to a lot of repeated checks, and in combination with our separate dependency check it's enough to exceed GitHub APi request rate limits during CI builds.remotes::install_local appears to not check dependencies at all when dependencies=FALSE, which is what we want for this case.
(Side note: The
force=TRUEis needed to make sure Make reinstalls your changes during local development, becauseinstall_localdefaults to not installing the package if its "SHA has not changed"... but for local packages it treats the package version string as the "SHA" and doesn't notice edits that don't change the version.)Description
Motivation and Context
Review Time Estimate
Types of changes
Checklist: