Section 1.3.3 of Writing R Extensions says
"The recommended method of building binary packages is to use
R CMD INSTALL --build pkg where pkg is either the name of a source tarball (in
the usual .tar.gz format) or the location of the directory of the package source
to be built. "
(a) vignettes are not created when R CMD INSTALL --build is run on a source
directory, so it seems that there is only one way to build full .zip files
(running R CMD INSTALL --build on the tar.gz file created by R CMD build). (b)
probably the intention was to have R CMD INSTALL --build pkg on a line by itself
Index: R-exts.texi
===================================================================
--- R-exts.texi (revision 64082)
+++ R-exts.texi (working copy)
@@ -2660,12 +2660,12 @@
The recommended method of building binary packages is to use
@command{R CMD INSTALL --build pkg}
+
@noindent
-where @file{pkg} is either the name of a source tarball (in the usual
-@file{.tar.gz} format) or the location of the directory of the package
-source to be built. This operates by first installing the package and
-then packing the installed binaries into the appropriate binary package
-file for the particular platform.
+where @file{pkg} is the name of a source tarball (in the usual
+@file{.tar.gz} format) produced by @command{R CMD build}. This operates
+by first installing the package and then packing the installed binaries
+into the appropriate binary package file for the particular platform.
By default, @command{R CMD INSTALL --build} will attempt to install the package
into the default library tree for the local installation of @R{}. This has two
--
Computational Biology / Fred Hutchinson Cancer Research Center
1100 Fairview Ave. N.
PO Box 19024 Seattle, WA 98109
Location: Arnold Building M1 B861
Phone: (206) 667-2793
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
