Uwe Ligges writes:
>> 2) As part of the binary package build process, run CHECK
>>with R_CHECK_FORCE_SUGGESTS = false.
> 1, 3-5 sound fine, but I do not see why you need 2).
I suppose because it makes me feel dirty to leave the check step out
entirely, if there is some utility available
Allen S. Rout wrote:
On Sep 2, 2009, at 2:53 , Allen S. Rout wrote:
I'm working to automate the building of RPM packages for CRAN &c.
In the process, I'm trying to get a sense of the correct
dependencies.
[...]
In other words, to check properly, I need to treat Suggests and
Imports as D
> On Sep 2, 2009, at 2:53 , Allen S. Rout wrote:
>
>> I'm working to automate the building of RPM packages for CRAN &c.
>> In the process, I'm trying to get a sense of the correct
>> dependencies.
>>
>> [...]
>>
>> In other words, to check properly, I need to treat Suggests and
>> Imports as Dep
Allen,
On Sep 2, 2009, at 2:53 , Allen S. Rout wrote:
I'm working to automate the building of RPM packages for CRAN &c.
In the process, I'm trying to get a sense of the correct dependencies.
It's my sense that R CMD CHECK is the Right Way to check to see if a
package is built properly. B
Allen S. Rout wrote:
I'm working to automate the building of RPM packages for CRAN &c. In
the process, I'm trying to get a sense of the correct dependencies.
It's my sense that R CMD CHECK is the Right Way to check to see if a
package is built properly. But according to Writing R Extension
