Run revdep checksSource:
R CMD check on all reverse dependencies of your
package. To avoid false positives, it runs
R CMD check twice: once for
released version on CRAN and once for the local development version. It
then reports the differences so you can see what checks were previously
ok but now fail.
Once your package has been successfully submitted to CRAN, you should
revdep_reset(). This deletes all files used for checking, freeing
up disk space and leaving you in a clean state for the next release.
Path to package.
Which types of revdeps should be checked. For CRAN release, we recommend using the default.
Suppress output from internal processes?
Maximum time to wait (in seconds) for
R CMD checkto complete. Default is 10 minutes.
Number of parallel workers to use
Also check revdeps that live in Bioconductor?
Environment variables to set for the install and check processes. See
revdep_check() proceeds in four steps:
Init: create the
revdep/subdirectory if it doesn't already exist, and save the list of reverse dependencies to check.
Install: install the CRAN (released) and local (development) versions of your package, including all dependencies.
R CMD checktwice for each reverse dependency, once for the CRAN version and one for the local version. The checks are run in parallel using
Report: generate reports showing differences between the check results for the CRAN and local versions of your package. The focus of the report is on new failures. The reports are saved in
revdep_check() is designed to seamlessly resume in the case of failure:
revdep_check() and it will start from where it left off.
If you want to start again from scratch, run