- libPaths
A new path to append to, or replace all existing user
components of .libPath()
- standAlone
Logical. If TRUE, all packages will be installed to and
loaded from the libPaths only. NOTE: If TRUE, THIS WILL CHANGE THE
USER'S .libPaths(), similar to e.g., the checkpoint package. If
FALSE, then libPath will be prepended to .libPaths() during the
Require call, resulting in shared packages, i.e., it will include the
user's default package folder(s). This can be create dramatically faster
installs if the user has a substantial number of the packages already in
their personal library. Default FALSE to minimize package installing.
- updateRprofile
Logical or Character string. If TRUE, then this
function will put several lines of code in the current directory's
.Rprofile file setting up the package libraries for this and future
sessions. If a character string, then this should be the path to an
.Rprofile file. To reset back to normal, run setLibPaths() without a
libPath. Default: getOption("Require.updateRprofile", FALSE), meaning
FALSE, but it can be set with an option or within a single call.
- exact
Logical. This function will automatically append the R version
number to the libPaths to maintain separate R package libraries for each
R version on the system. There are some cases where this behaviour is not
desirable. Set exact to TRUE to override this automatic appending and
use the exact, unaltered libPaths. Default is FALSE
- verbose
Numeric or logical indicating how verbose should the function
be. If -1 or -2, then as little verbosity as possible. If 0 or FALSE,
then minimal outputs; if 1 or TRUE, more outputs; 2 even more. NOTE: in
Require function, when verbose >= 2, also returns details as if
returnDetails = TRUE (for backwards compatibility).