1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
|
% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/updatePkgDepends.R
\name{updatePackages}
\alias{updatePackages}
\title{Update packages, spot new dependencies, and install them}
\usage{
updatePackages(
ask = FALSE,
checkBuilt = TRUE,
dependencies = c("Depends", "Imports", "LinkingTo"),
libnew = "/usr/share/R/library/",
repos = options("repos"),
...
)
}
\arguments{
\item{ask}{If TRUE, asks user to select packages to update}
\item{checkBuilt}{If TRUE, packages built under earlier versions
of R are to be considered 'old'}
\item{dependencies}{A vector specifying which type of dependencies
need to be taken into account. We default to c("Depends",
"Imports", "LinkingTo").}
\item{libnew}{The R library folder into which the new packages
must be installed. Defaults to "/usr/share/R/library", which
is where EL7 likes those things. To install packages in
personal user directory, put libnew = NULL.}
\item{repos}{A vector of repositories on which to search for
packages. Same definition as in R's install.packages or
install.packages.}
\item{...}{additional arguments passed to update.packages and
install.packages}
}
\value{
A vector of new packages being installed
}
\description{
Addresses the problem that updates for previously installed R
packages may insert new dependencies. R's update.packages does not
trigger the installation of packages that are added as new
requirements in existing packages.
}
\details{
This function checks for existence of updates, ascertains whether
those packages impose new requirements, and installs any new
requirements. Then it conducts the update.
This function is valuable in system maintenance because sometimes
existing packages adopt new requirements and the update.packages
function does not notice. Another possible case would be that a user
accidentally deletes some packages without realizing other packages
depend on them.
If this is run as the root/administrator privileged, then base R
packages may be updated, but if user is not root/administrator,
there will be a warning that packages were not updated because
permissions were lacking. For example
"Warning: package 'boot' in library '/usr/lib/R/library' will not
be updated.
This warning does not interfere with rest of purpose of this
function, since the new dependencies can be installed in a place
where the user has privileges, either by specifying libnew as a
full directory name or by setting it to NULL, which puts new
packages in $R_LIBS_USER
}
\examples{
\dontrun{
myrepos <- c("http://rweb.crmda.ku.edu/cran",
"http://www.bioconductor.org/packages/3.3/bioc")
updatePackages(repos = myrepos)
## libnew defaults to "/usr/share/R/library". Specify NULL
## so that new packages will go to user's directory
updatePackages(libnew = NULL)
}
}
\author{
Paul Johnson <pauljohn@ku.edu>
}
|
