On 04/04/2016 01:56 PM, Duncan Murdoch wrote:
On 04/04/2016 1:35 PM, Dirk Eddelbuettel wrote:
On 4 April 2016 at 07:25, Hadley Wickham wrote:
| On Sat, Apr 2, 2016 at 5:33 AM, Jan Górecki
wrote:
|
| In principle, I believe a package should pass R CMD check if no
|
On 04/04/2016 1:35 PM, Dirk Eddelbuettel wrote:
On 4 April 2016 at 07:25, Hadley Wickham wrote:
| On Sat, Apr 2, 2016 at 5:33 AM, Jan Górecki wrote:
|
| In principle, I believe a package should pass R CMD check if no
| suggested packages are installed. However, since this
On 4 April 2016 at 07:25, Hadley Wickham wrote:
| On Sat, Apr 2, 2016 at 5:33 AM, Jan Górecki wrote:
|
| In principle, I believe a package should pass R CMD check if no
| suggested packages are installed. However, since this is not currently
The relevant manual says
Jan and Hadley,
There's also the issue of tests, vignettes, or examples requiring Suggested
packages (one of the core applications of Suggests, in fact). These are all
checked by R CMD check, so to ensure any package which should pass check
would do so without suggested packages installed would
On Sat, Apr 2, 2016 at 5:33 AM, Jan Górecki wrote:
> Dear R team,
>
> Are suggested dependencies mandatory in context of `R CMD check` when
> using env var `_R_CHECK_FORCE_SUGGESTS_=FALSE`?
>
> Suggested dependencies are nice because are optional.
> But that feature often
Dear R team,
Are suggested dependencies mandatory in context of `R CMD check` when
using env var `_R_CHECK_FORCE_SUGGESTS_=FALSE`?
Suggested dependencies are nice because are optional.
But that feature often isn't valid when trying to run `R CMD check` on them.
I would like to use `export