Hello,
this is *not* a new behavior on CRAN, at least on (re-)submissions to
CRAN. The package has to pass R CMD check --as-cran with all OK. If
one of the Suggests:ed package is not installed, but one of your
examples or package tests needed it, that would be detected by the
check system.
The
Hi John,
You need to set the R CMD check environment variable
_R_CHECK_FORCE_SUGGESTS_ to FALSE/0. You should be able to do this
with the env_vars
argument in rhub::check(). You can also achieve this with github actions by
customizing your yaml file (example here:
I want to check my package to make sure I'm properly using suggested
packages. I'm trying to catch mistakes where I forgot to do what you're
suggesting.
On Tue, Jul 18, 2023 at 7:58 AM Serguei Sokol
wrote:
> Is it possible that you have complicated the task unnecessarily?
> Normally, you can
В Tue, 18 Jul 2023 07:37:40 -0700
John Harrold пишет:
> I was wondering if anyone has a good way to run R CMD
> check with only the imports installed?
According to "R Internals", running R CMD check with the environment
variable _R_CHECK_DEPENDS_ONLY_ set to "TRUE" will populate a temporary
Is it possible that you have complicated the task unnecessarily?
Normally, you can just do
if (requireNamespace("", quietly=TRUE)) {
# do the tests involving
}
Wasn't that enough?
Best,
Serguei.
Le 18/07/2023 à 16:37, John Harrold a écrit :
Howdy Folks,
I recent had a package start
Howdy Folks,
I recent had a package start failing because I wasn't checking properly in
my tests to make sure my suggested packages were installed before running
tests. I think this is something new running on CRAN where packages are
tested with only the packages specified as Imports in the
