Dependency analysis on package deldir
General information
| CRAN link | link |
|---|---|
| Package version | 1.0-6 |
| Number of strong dependencies | 2 |
| Number of all dependencies | 3 |
| Number of parent packages | 2 |
| Max heaviness from parent packages | 1 |
| Total heaviness from parent packages | 2 |
Number of parent packages (including Suggests and Enhances) | 3 |
Dependency heatmap
In the following dependency heatmap, rows are the parent packages of deldir and columns are the dependency packages that each parent package brings in. On the right side of the heatmap, there are three barplot annotations: 1. number of imported functions/S4 methods/S4 classes from parent packages; 2. number of dependency packages from each parent package; 3. heaviness of each parent package on deldir.
Dependency table
"Import" information is from the NAMESPACE file of deldir.
imports: number of imported functions/objects; importMethods: number of imported S4 methods; importClasses: number of imported S4 classes.
Required packages: number of strong dependency packages for each of the parent package (or in other words, number of dependency packages the parent package brings in).
Heaviness from parent on deldir: number of required packages that can be reduced if moving parent package to Suggests of deldir.
| Parent package | Field | imports | importMethods | importClasses | Required packages | Heaviness from parent on deldir |
|---|---|---|---|---|---|---|
| graphics | Imports | 10 | 0 | 0 | 0 | 1 |
| grDevices | Imports | 2 | 0 | 0 | 0 | 1 |
| polyclip | Suggests | No object is imported into the namespace of deldir. | 0 | 1 | ||
Analysis was done with pkgndep.