-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Description
In some cases, not all suggested packages may be needed to be installed. Especially if significant system dependency load is introduced. For example, the sf package puts a significant GIS-based strain on installation of ggplot2.
In more extreme cases, wrapper packages, such as broom which provide interfaces over many packages can have huge suggested package loads
For example, the tidyverse broom package introduces the following suggested dependencies:
Suggests:
AER,
akima,
AUC,
bbmle,
betareg,
biglm,
binGroup,
boot,
brms,
btergm,
coda,
covr,
emmeans,
ergm,
gam,
gamlss,
geepack,
ggplot2,
glmnet,
gmm,
Hmisc,
irlba,
knitr,
ks,
Lahman,
lfe,
lme4,
lmodel2,
lmtest,
lsmeans,
maps,
maptools,
MASS,
Matrix,
mclust,
mgcv,
muhaz,
multcomp,
network,
nnet,
orcutt,
plm,
poLCA,
psych,
purrr,
rgeos,
rmarkdown,
robust,
rsample,
rstan,
rstanarm,
sp,
speedglm,
statnet.common,
survival,
testthat,
xergm,
zoo,
tseries
This has arisen even in full-filled images, such as rocker/verse, where the xergm package does not install as of 2018-07-08
One solution is to provide a configuration option to check against a list of blacklisted packages before appending the suggested packages to the metapackage.
Metadata
Metadata
Assignees
Labels
No labels