buildRiskReport: Build risk-assessment for proposed package updates
In gmbecker/gRAN: Creating Continuously Integrated Package Repositories from Manifests

buildRiskReport

R Documentation

Build risk-assessment for proposed package updates

Description

buildRiskReport

Usage

buildRiskReport(repo, to_update = old.packages(repos = repo_urls),
  important_pkgs = installed.packages(lib.loc = liblocs)[, "Package"],
  liblocs = .libPaths(), repo_urls = getOption("repos"),
  report_file = file.path(destination(repo), "update-risk.html"),
  theme = "bootstrap")

Arguments

`repo`	The name of a GRAN repository to use. Assumes that a a package named GRAN<repo> is available to load.
`to_update`	vector of package names which may be updated, or a matrix output from `old.packages`. Defaults to all packages which are out of date
`important_pkgs`	list of packages to check for risk of change cascades from updating the packages in `to_update`. Defaults to all installed packages
`liblocs`	the library locations to look for installed packages
`repo_urls`	The repositories to check for new versions of packages
`report_file`	File where HTML report will be written to
`theme`	CSS theme. bootstrap, foundation, semanticui or jqueryui

Details

Generates an HTML report identifying which packages have updates available, and which of the specified important packages may be effected by installing those new versions.