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)
.
Usage
setup(
newLibPaths,
RPackageFolders,
RPackageCache = cacheGetOptionCachePkgDir(),
standAlone = getOption("Require.standAlone", TRUE),
verbose = getOption("Require.verbose")
)
setupOff(removePackages = FALSE, verbose = getOption("Require.verbose"))
Arguments
- newLibPaths
Same as
RPackageFolders
. This is for more consistent naming withRequire(..., libPaths = ...)
.- RPackageFolders
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.
- RPackageCache
See
?RequireOptions
.- standAlone
Logical. If
TRUE
, all packages will be installed to and loaded from thelibPaths
only. NOTE: IfTRUE
, THIS WILL CHANGE THE USER'S.libPaths()
, similar to e.g., thecheckpoint
package. IfFALSE
, thenlibPath
will be prepended to.libPaths()
during theRequire
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. DefaultFALSE
to minimize package installing.- 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: inRequire
function, whenverbose >= 2
, also returns details as ifreturnDetails = TRUE
(for backwards compatibility).- removePackages
Deprecated. Please remove packages manually from the .libPaths()