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

Feature request: renv::status() - report upgraded vs. downgraded packages more clearly #2063

Open
HenningLorenzen-ext-bayer opened this issue Dec 18, 2024 · 0 comments

Comments

@HenningLorenzen-ext-bayer
Copy link
Contributor

I would like to see more clearly whether packages (installed in the library) have been upgraded or downgraded relative to the lockfile specification.

Doing the math on version numbers myself is cumbersome, I would like renv to do this for me.

Example from renv 1.0.11

# CRAN -----------------------------------------------------------------------
- cluster       [2.0.8 != 2.1.0]
- ellipsis      [0.3.0 != 0.3.1]
- foreign       [0.8-71 != 0.8-75]
- git2r         [0.26.1 != 0.27.1]
- haven         [2.2.0 != 2.3.1]
- jsonlite      [1.6.1 != 1.7.0]
- KernSmooth    [2.23-18 != 2.23-16]
- lubridate     [1.7.8 != 1.7.9]
- MASS          [7.3-51.4 != 7.3-51.5]
- Matrix        [1.2-17 != 1.2-18]
- matrixStats   [0.58.0 != 0.56.0]
- mgcv          [1.8-28 != 1.8-31]
- nlme          [3.1-139 != 3.1-144]
- nloptr        [1.2.1 != 1.2.2.1]
- openssl       [1.4.1 != 1.4.2]
- pkgbuild      [1.0.7 != 1.0.8]
- ps            [1.3.2 != 1.3.3]
- renv          [0.13.2 != 1.0.11]
- sp            [1.4-5 != 1.4-2]
- survival      [3.1-12 != 3.1-8]
- zip           [2.1.1 != 2.2.0]

Mock-up 1: Replace != with relational operators

# CRAN -----------------------------------------------------------------------
- cluster       [2.0.8 < 2.1.0]
- ellipsis      [0.3.0 < 0.3.1]
- foreign       [0.8-71 < 0.8-75]
- git2r         [0.26.1 < 0.27.1]
- haven         [2.2.0 < 2.3.1]
- jsonlite      [1.6.1 < 1.7.0]
- KernSmooth    [2.23-18 > 2.23-16]
- lubridate     [1.7.8 < 1.7.9]
- MASS          [7.3-51.4 < 7.3-51.5]
- Matrix        [1.2-17 < 1.2-18]
- matrixStats   [0.58.0 > 0.56.0]
- mgcv          [1.8-28 < 1.8-31]
- nlme          [3.1-139 < 3.1-144]
- nloptr        [1.2.1 < 1.2.2.1]
- openssl       [1.4.1 < 1.4.2]
- pkgbuild      [1.0.7 < 1.0.8]
- ps            [1.3.2 < 1.3.3]
- renv          [0.13.2 < 1.0.11]
- sp            [1.4-5 > 1.4-2]
- survival      [3.1-12 > 3.1-8]
- zip           [2.1.1 < 2.2.0]

Mock-up 2: group downgraded vs. upgraded

# CRAN -----------------------------------------------------------------------
## Library packages have been upgraded ---------------------------------------
- cluster       [2.0.8 < 2.1.0]
- ellipsis      [0.3.0 < 0.3.1]
- foreign       [0.8-71 < 0.8-75]
- git2r         [0.26.1 < 0.27.1]
- haven         [2.2.0 < 2.3.1]
- jsonlite      [1.6.1 < 1.7.0]
- lubridate     [1.7.8 < 1.7.9]
- MASS          [7.3-51.4 < 7.3-51.5]
- Matrix        [1.2-17 < 1.2-18]
- mgcv          [1.8-28 < 1.8-31]
- nlme          [3.1-139 < 3.1-144]
- nloptr        [1.2.1 < 1.2.2.1]
- openssl       [1.4.1 < 1.4.2]
- pkgbuild      [1.0.7 < 1.0.8]
- ps            [1.3.2 < 1.3.3]
- renv          [0.13.2 < 1.0.11]
- zip           [2.1.1 < 2.2.0]
## Library packages have been downgraded -------------------------------------
- KernSmooth    [2.23-18 > 2.23-16]
- matrixStats   [0.58.0 > 0.56.0]
- sp            [1.4-5 > 1.4-2]
- survival      [3.1-12 > 3.1-8]
@HenningLorenzen-ext-bayer HenningLorenzen-ext-bayer changed the title Feature request: renv::status() - report upgraded vs. downgraded packages more clearly Feature request: renv::status() - report upgraded vs. downgraded packages more clearly Dec 18, 2024
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