Run bootstrap.R file on build if present and specified in Config/build #157
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.
For r-lib/pkgdepends#303 . Basically, I'm spending a lot of time working in repositories that share sources between Python and R packages and it would be nice if the pak-based tooling worked out-of-the box for things like
Remotes:
dependencies and check/build/install actions.The general approach is:
bootstrap.R
andConfig/build/bootstrap: TRUE
callr::rscript()
to runboostrap.R
with the working directory set to the source directoryThe DESCRIPTION Config option is nice because it makes the opt-in more explicit (in the event that bootstrap.R existed in the package directory already) and because there was already a place to document Config/build options.
As @gaborcsardi pointed out, using
Rscript
+ "boostrap.R" is more portable than a shell script because Rtools might not be installed or on the PATH.This approach doesn't help with
R CMD INSTALL pkg_directory
but package authors can always do$R_HOME/bin/Rscript bootstrap.R
inconfigure
and/orconfigure.win
, which also would work withdevtools::load_all()
(I think).