setup and setupOff are currently deprecated.
These may be re-created in a future version.
In its place, a user can simply put .libPaths(libs, include.site = FALSE)
in their .Rprofile file, where libs is the directory where the packages
should be installed and should be a folder with the R version number, e.g.,
derived by using checkLibPaths(libs).
setup(
newLibPaths,
RPackageFolders,
RPackageCache = getOptionRPackageCache(),
standAlone = getOption("Require.standAlone", TRUE),
verbose = getOption("Require.verbose")
)
setupOff(removePackages = FALSE, verbose = getOption("Require.verbose"))Same as RPackageFolders. This is for more consistent
naming with Require(..., libPaths = ...).
One or more folders where R packages are installed to and loaded from. In the case of more than one folder provided, installation will only happen in the first one.
See ?RequireOptions.
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.
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, the return object will have an
attribute: attr(.., "Require") which has lots of information about the
processes of the installs.
Deprecated. Please remove packages manually from the .libPaths()