[Bioc-devel] _R_CHECK_FORCE_SUGGESTS_ = false

Henrik Bengtsson hb at biostat.ucsf.edu
Sat Sep 15 17:29:57 CEST 2012

Here's another example of this:


Question to BioC core: Why not sticking with the default
_R_CHECK_FORCE_SUGGESTS_=FALSE?  I see a suggested package as a
package that is not required except in rare cases.  I also sometimes
use them to complement each other, e.g. part of my code prefer package
A but if that doesn't exist it's fall back to use package B.  It's up
to the developer to write examples()/system tests that don't generate
R CMD check errors in these cases, and if they forget, then ...yes...
R CMD check will generate an ERROR anyway.


On Sat, Sep 15, 2012 at 7:40 AM, Yue Li <gorillayue at gmail.com> wrote:
> Dear list,
> I just submitted a new package. It builds and checks OK on the Mac and Linux servers but fails to build on the Windows server, namely 'mosacto1'. The error says:
> * checking package dependencies ... ERROR
> Package suggested but not available: 'multicore'
> The suggested packages are required for a complete check.
> Checking can be attempted without them by setting the environment
> variable _R_CHECK_FORCE_SUGGESTS_ to a false value.
> But it seems that I can only set that environment variable _R_CHECK_FORCE_SUGGESTS_ in ~/.R/check.Renviron on my local machine not on the server. I wonder if anyone encountered the same problem when trying to submit your package before? I apologize if the issue has been addressed in some other posts that I failed to find it by Google.
> Thanks in advance,
> Yue
> _______________________________________________
> Bioc-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/bioc-devel

More information about the Bioc-devel mailing list