On Jan 15, 2010, at 12:18 , Ross Boylan wrote:
On Fri, 2010-01-15 at 09:19 +0100, Kurt Hornik wrote:
The idea is that maintainers typically want to
fully check their functionality, suggesting to force suggests by
default.
This might be the nub of the problem. There are different audiences,
even for R CMD check.
The maintainer probably wants to check all functionality. Even then,
there is an issue if functionality differs by platform.
CRAN probably wants to check all functionality.
An individual user just wants to check the functionality they use.
For example, if someone doesn't want to run my package distributed,
but
wants to see if it works (R CMD check), they need to be able to avoid
the potentially onerous requirement to install MPI.
... that what's why you can decide to run check without forcing
suggests - it's entirely up to you / the user as Kurt pointed out ...
Cheers,
Simon
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
