Open bcdarwin opened 3 years ago
It should be noted that R CMD INSTALL
only tests that the package can be loaded, R CMD check
is needed to run the actual tests and an assortment of other QC checks.
I marked this as stale due to inactivity. → More info
My understanding is that R CMD CHECK Is needed for package development to ensure that the package complies with R package requirements. R CMD INSTALL may be sufficient here, as our goal is to install packages, not to submit them to CRAN. In other words, a package that fails R CMD CHECK may still be perfectly usable.
R CMD check
also tests the packages, unlike R CMD INSTALL
. We can of course disable extraneous or CRAN-specific checks (e.g. --no-manual
, etc.).
Describe the bug
In
pkgs/development/r-modules/generic-builder.nix
we find:but this is not actually true; when building any package one doesn't see the output of running
R CMD check <r-cmd-build-output.tar.gz>
To Reproduce
nix-build -A rPackages.lenses '\<nixpkgs>' --pure
Expected behavior
We should see the output of running R CMD check, i.e.
Notify maintainers
@peti
Maintainer information: