Skip to content

blacklist suggested packages #3

@dpastoor

Description

@dpastoor

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

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions