You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a DESCRIPTION file specifies a minimum version of R in Depends, renv::dependencies() returns R as a "Package", though that's not completely correct since there is no R package named "R". I suspect there's some good reason for renv::dependencies() to include the specified minimum version of R in its return value/object, but it would be nice if it was somehow clearly marked as not-really-a-package. I was using renv::dependencies()[['Package']] to feed into e.g. pak::pak(renv::dependencies()[['Package']]), which worked fine until I added a DESCRIPTION file to a non-R-package project that specified a minimum R version.
The text was updated successfully, but these errors were encountered:
When a DESCRIPTION file specifies a minimum version of R in
Depends
,renv::dependencies()
returnsR
as a "Package", though that's not completely correct since there is no R package named "R". I suspect there's some good reason forrenv::dependencies()
to include the specified minimum version of R in its return value/object, but it would be nice if it was somehow clearly marked as not-really-a-package. I was usingrenv::dependencies()[['Package']]
to feed into e.g.pak::pak(renv::dependencies()[['Package']])
, which worked fine until I added a DESCRIPTION file to a non-R-package project that specified a minimum R version.The text was updated successfully, but these errors were encountered: