R CMD build --resave-data

Hadley Wickham · 2011-04-13T02:26:46Z

>> If you deliberately ignore the fact that 'R CMD INSTALL' is also used >> by developers to install from the *package source tree* (by opposition >> to end users who use it to install from a *source tarball*, > > .. for a good reason, IMHO no serious developer would do that for obvious reasons - you'd be working on a dirty copy creating many unnecessary problems and polluting your sources. The first time you'll spend an hour chasing a non-existent problem due to stale binary objects in your tre

Hadley Wickham

Tue, Apr 12, 2011 7:26 PM

This is news to me!  I know that you're supposed to run R CMD check on
the built package, but you're supposed to run install on it too?  (And
if it's so important, why doesn't R do it for you automatically?)

Do you have any convenient shortcuts to overcome the fact that the
binary package contains the package name?  i.e. how can I build and
install/check in a single line without having to specify the full file
name?

How can I go from:

R CMD build plyr && R CMD install plyr_1.5.tar.gz

to

R CMD build-and-install plyr ?

Hadley

Assistant Professor / Dobelman Family Junior Chair
Department of Statistics / Rice University
http://had.co.nz/

Thread (10 messages)

Hervé Pagès R CMD build --resave-data Apr 10 Uwe Ligges R CMD build --resave-data Apr 11 Hervé Pagès R CMD build --resave-data Apr 12 Simon Urbanek R CMD build --resave-data Apr 12 Hadley Wickham R CMD build --resave-data Apr 12 Simon Urbanek R CMD build --resave-data Apr 12 Hervé Pagès R CMD build --resave-data Apr 12 Martin Maechler R CMD build --resave-data Apr 13 Uwe Ligges R CMD build --resave-data Apr 13 Hervé Pagès R CMD build --resave-data Apr 13