From seth at userprimary.net  Sat Jan 16 16:37:09 2010
From: seth at userprimary.net (Seth Falcon)
Date: Sat, 16 Jan 2010 07:37:09 -0800
Subject: [Rd] optional package dependency
In-Reply-To: <4B508F1C.1030604@statistik.tu-dortmund.de>
References: <1263535210.26202.16.camel@corn.betterworld.us>	<e8e755251001142212nd942256i526d63f4858f988c@mail.gmail.com>	<19280.9467.920615.289850@hornik.net>
	<4B50881B.1070106@userprimary.net>
	<4B508F1C.1030604@statistik.tu-dortmund.de>
Message-ID: <4B51DD25.8050902@userprimary.net>

On 1/15/10 7:51 AM, Uwe Ligges wrote:
> the Windows checks for CRAN run with that setting, i.e.
> 
>  _R_CHECK_FORCE_SUGGESTS_=false
> 
> Hence the multicore issue mentioned below actually does not exist.

I did not know that the Windows checks for CRAN used this setting.
My concern was initiated by a Bioconductor package developer wanting to
use multicore and I mistakenly thought the issue would exist for CRAN as
well.  Bioconductor currently uses the default configuration for check
on all platforms.  For the CRAN case, there is no immediate problem.

While there isn't an issue at hand, the approach still seems lacking.
What happens when there is a Windows only package that folks want to
optionally use?  Perhaps public repositories should then not force
suggests for any platforms (do they already?) -- I think that is a
reasonable and simple solution.  But in that case, perhaps the deafult
value should change.

+ seth



[Rd] optional package dependency
Seth Falcon