On 11-04-29 10:36 PM, Prof Brian Ripley wrote:
On Fri, 29 Apr 2011, Hervé Pagès wrote:
On 11-03-30 01:55 AM, Prof Brian Ripley wrote:
What R CMD build (and check) does is to call tools::buildVignettes.
That has been true for a while, and buildVignettes() returns if no
vignettes are found. The
On 11-03-30 01:55 AM, Prof Brian Ripley wrote:
What R CMD build (and check) does is to call tools::buildVignettes.
That has been true for a while, and buildVignettes() returns if no
vignettes are found. The docs are out-of-date.
My view is that you are misusing inst/doc: it is intended *only*
On Fri, 29 Apr 2011, Hervé Pagès wrote:
On 11-03-30 01:55 AM, Prof Brian Ripley wrote:
What R CMD build (and check) does is to call tools::buildVignettes.
That has been true for a while, and buildVignettes() returns if no
vignettes are found. The docs are out-of-date.
My view is that you are
Hi,
in Section 'Writing package vignettes' of 'Writing R Extensions' it says:
Whenever a Makefile is found, then R CMD build will try to run make
after the Sweave runs, so PDF manuals can be created from arbitrary
source formats (plain LaTeX files, ...). [...] Note that the make step
is executed
What R CMD build (and check) does is to call tools::buildVignettes.
That has been true for a while, and buildVignettes() returns if no
vignettes are found. The docs are out-of-date.
My view is that you are misusing inst/doc: it is intended *only* for
files which are going to be installed and
