Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

blacklist suggested packages #3

Open
dpastoor opened this issue Jun 8, 2018 · 0 comments
Open

blacklist suggested packages #3

dpastoor opened this issue Jun 8, 2018 · 0 comments

Comments

@dpastoor
Copy link
Member

dpastoor commented Jun 8, 2018

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant