check_packages_in_dir allows to conveniently check source
package .tar.gz files in the given directory dir, along
with their reverse dependencies as controlled by reverse.
The "which" component of reverse can also be a list, in
which case reverse dependencies are obtained for each element of the
list and the corresponding element of the "recursive" component
of reverse (which is recycled as needed).
If needed, the source .tar.gz files of the reverse dependencies
to be checked as well are downloaded into dir (and removed at
the end if clean is true). Next, all packages (additionally)
needed for checking are installed to the Library subdirectory
of dir. Then, all .tar.gz files are checked using the
given arguments and environment variables, with outputs and messages
to files in the Outputs subdirectory of dir. The
*.Rcheck directories with the check results of the reverse
dependencies are renamed by prefixing their base names with
rdepends_.
Results and timings can conveniently be summarized using
summarize_check_packages_in_dir_results and
summarize_check_packages_in_dir_timings, respectively.
Installation and checking is performed in parallel if Ncpus is
greater than one: this will use mclapply on
Unix and parLapply on Windows.
check_packages_in_dir returns an object inheriting from class
"check_packages_in_dir" which has print and
summary methods.
check_packages_in_dir_changes allows to analyze the effect of
changing (some of) the sources. With dir and old the
paths to the directories with the new and old sources, respectively,
and the corresponding check results, possible changes in the check
results can conveniently be analyzed as controlled via options
outputs and sources. The changes object returned can be
subscripted according to change in severity from the old to the new
results by using one of "==", "!=", "<",
"<=", ">" or ">=" as row index.
check_packages_in_dir_details analyzes check log files to
obtain check details as a data frame which can be used for further
processing, providing check name, status and output for every check
performed and not dropped according to status tag (via variables
Check, Status and Output, respectively).
Environment variable _R_CHECK_ELAPSED_TIMEOUT_ can be used to
set a limit on the elapsed time of each check run. See the
‘R Internals’ manual for how the value is interpreted and for
other environment variables which can be used for finer-grained
control on timeouts within a check run.