Gábor Csárdi

My guess would be that it is a bug in the `R CMD check` output parser, but if I call the parser manually on your file, then it works well:...

We create two new isolated libraries, one for the checks with the CRAN version and one for the new version of your package. But we can't really isolate them completely...

Can you try to run this check again, with a clean `.Library`, to see it is reproducible? ``` revdep_add(, "broomExtra") revdep_check() ```

> out of curiosity, does no-one use --vanilla any more, or if they do how do they handle the use of non-base/recommended packages? Keep your non-core packages at `R_LIBS_USER`: ```...

The CRAN machines have a different setup, so I am not sure if it worth comparing them to our results. We would see a lot of false positives, I am...

> but we check issue on our side for the CRAN revdep check If you detect an issue during revdepcheck, then you investigate, I assume, so you would go to...

That's often problematic is that system requirements are not available. Nevertheless you can make your own choice by setting the corresponding option or env var. See `install.packages.compile.from.source` in `?options`.

Yeah, although shouldn't the package itself set this?

You can also just set this before starting the check, env vars are inherited.

This does not seem very important currently, but eventually we can have a `?novignettes` and a `?vignettes` parameter, these are pretty simple to implement.