On Tue, 2005-09-20 at 10:03 -0400, Roger D. Peng wrote:
> I think the reason is that the standard for 'R CMD check' is that examples in
> help pages are guaranteed to be executable by the user (as long as the
> requirements are met). There is no way to guarantee this without having the
> packag
> Roger D Peng writes:
> I think the reason is that the standard for 'R CMD check' is that
> examples in help pages are guaranteed to be executable by the user (as
> long as the requirements are met). There is no way to guarantee this
> without having the packages installed. So strictly spea
Seth Falcon wrote:
>On 20 Sep 2005, [EMAIL PROTECTED] wrote:
>
>
>>As I said above, and will try to emphasize, I really do not want R
>>CMD check to do any checking of Uses (unless asked to do
>>so). Developers that use Uses need to make sure that their package
>>works and passes R CMD check whe
On 20 Sep 2005, [EMAIL PROTECTED] wrote:
> As I said above, and will try to emphasize, I really do not want R
> CMD check to do any checking of Uses (unless asked to do
> so). Developers that use Uses need to make sure that their package
> works and passes R CMD check whether the package is there o
Prof Brian Ripley wrote:
> On Tue, 20 Sep 2005, Jari Oksanen wrote:
>
>
>>On Tue, 2005-09-20 at 09:42 -0400, Roger D. Peng wrote:
>>
>>>I think this needs to fail because packages listed in 'Suggests:' may, for
>>>example, be needed in the examples. How can 'R CMD check' run the examples
>>>a
On Tue, 20 Sep 2005, Jari Oksanen wrote:
> On Tue, 2005-09-20 at 09:42 -0400, Roger D. Peng wrote:
> > I think this needs to fail because packages listed in 'Suggests:' may, for
> > example, be needed in the examples. How can 'R CMD check' run the examples
> > and
> > verify that they are execut
On 9/20/05, Jari Oksanen <[EMAIL PROTECTED]> wrote:
> On Tue, 2005-09-20 at 09:42 -0400, Roger D. Peng wrote:
> > I think this needs to fail because packages listed in 'Suggests:' may, for
> > example, be needed in the examples. How can 'R CMD check' run the examples
> > and
> > verify that they
I think the reason is that the standard for 'R CMD check' is that examples in
help pages are guaranteed to be executable by the user (as long as the
requirements are met). There is no way to guarantee this without having the
packages installed. So strictly speaking, the 'Suggested' packages ar
On Tue, 20 Sep 2005, Jari Oksanen wrote:
> On Tue, 2005-09-20 at 09:42 -0400, Roger D. Peng wrote:
>> I think this needs to fail because packages listed in 'Suggests:' may, for
>> example, be needed in the examples. How can 'R CMD check' run the examples
>> and
>> verify that they are executable
On Tue, 2005-09-20 at 09:42 -0400, Roger D. Peng wrote:
> I think this needs to fail because packages listed in 'Suggests:' may, for
> example, be needed in the examples. How can 'R CMD check' run the examples
> and
> verify that they are executable if those packages are not available? I
> su
I think this needs to fail because packages listed in 'Suggests:' may, for
example, be needed in the examples. How can 'R CMD check' run the examples and
verify that they are executable if those packages are not available? I suppose
you could put the examples in a \dontrun{}.
-roger
Jari Oks
The R-exts manual says about 'Suggests' field in package DESCRIPTION:
"The optional `Suggests' field uses the same syntax as `Depends' and
lists packages that are not necessarily needed."
However, this seems to be a suggestion you cannot refuse. If you suggest
packages:
(a line from DESCRIPTION)
12 matches
Mail list logo