Hi, just started using some functionality from this package and it looks like a very solid set of checks.
I noticed that backports is a hard dependency, but for projects running on the latest version of R that is unnecessary, everything will just be running through the base R versions of commands.
Is it possible to make it a suggested dependency such that it could be skipped or uninstalled? I'm trying to keep the footprint of third party packages down as low as possible in a project for work and this is the only package that requires backports at the moment for me. In this particular case I'm using renv with a declared R version dependency of R >= 4.5 in my project, but not sure if that can be used for dependency resolution in this case - I'm still quite new to the R/renv ecosystem.
Hi, just started using some functionality from this package and it looks like a very solid set of checks.
I noticed that backports is a hard dependency, but for projects running on the latest version of R that is unnecessary, everything will just be running through the base R versions of commands.
Is it possible to make it a suggested dependency such that it could be skipped or uninstalled? I'm trying to keep the footprint of third party packages down as low as possible in a project for work and this is the only package that requires backports at the moment for me. In this particular case I'm using renv with a declared R version dependency of R >= 4.5 in my project, but not sure if that can be used for dependency resolution in this case - I'm still quite new to the R/renv ecosystem.