Display installed locations of a package
Usage
pkg_status(pkg, lib = .libPaths())
Value
Data frame with data about installations of pkg
.
It has always has columns:
biocviews
: the corresponding field fromDESCRIPTION
, it must be present for all Bioconductor packages, other packages typically don't have it.built
: theBuilt
field fromDESCRIPTION
.depends
,suggests
,Imports
,linkingto
,enhances
: the corresponding fields from theDESCRIPTION
files.deps
: A list or data frames, the dependencies of the package. It has columns:ref
,type
(dependency type in lowercase),package
(dependent package, orR
),op
andversion
, for last two are for version requirement.op
can be>=
,>
,==
or<=
, although the only the first one is common in practice.library
: path to the package library containing the package.license
: fromDESCRIPTION
.md5sum
: fromDESCTIPTION
, typicallyNA
, except on Windows.needscompilation
: fromDESCRIPTION
, this column is logical.package
: package name.platform
: from theBuilt
field inDESCRIPTION
, the current platform if missing fromDESCRIPTION
.priority
: fromDESCRIPTION
, usuallybase
,recommended
, or missing.ref
: the correspondinginstalled::*
package reference.repository
: fromDESCRIPTION
. For packages from a CRAN repository this isCRAN
, some other repositories, e.g. R-universe adds the repository URL here.repotype
:cran
,bioc
or missing.rversion
: from theBuilt
field. If no such field, then the current R version.sysreqs
: theSystemRequirements
field fromDESCRIPTION
.title
: package title.type
: alwaysinstalled
.version
: package version (as string).
DESCRIPTION
, but
pak also adds a couple.
Notes:
In addition, it also has all
remote*
andconfig/needs/*
entries from theDESCRIPTION
files. (Case insensitive.)All columns are of type
character
, except forneedscompilation
, which is logical anddeps
, which is a list columns.If an entry is missing for a package, it is set to
NA
.Note that column names are lowercase, even if the corresponding entries are not in
DESCRIPTION
.The order of the columns is not deterministic, so don't assume any order.
Additional columns might be present, these are internal for pak and should not be used in user code.
Examples
pkg_status("MASS")
#> # A data frame: 2 × 39 #> library package title version depends repos…¹ license needs…² built #> * <chr> <chr> <chr> <chr> <chr> <chr> <chr> <lgl> <chr> #> 1 /Users/ga… MASS Supp… 7.3-58… R (>= … CRAN GPL-2 … TRUE R 4.… #> 2 /Library/… MASS Supp… 7.3-58… R (>= … CRAN GPL-2 … TRUE R 4.… #> # … with 30 more variables: remotetype <chr>, remotepkgref <chr>, #> # remoteref <chr>, remoterepos <chr>, remotepkgplatform <chr>, #> # remotesha <chr>, imports <chr>, suggests <chr>, linkingto <chr>, #> # remotes <chr>, remotehost <chr>, remoterepo <chr>, #> # remoteusername <chr>, enhances <chr>, biocviews <chr>, #> # remoteurl <chr>, remotesubdir <chr>, priority <chr>, #> # remoteetag <chr>, remotepackaged <chr>, md5sum <chr>, …
See also
Other package functions:
lib_status()
,
pak()
,
pkg_deps_tree()
,
pkg_deps()
,
pkg_download()
,
pkg_install()
,
pkg_remove()
,
pkg_sysreqs()