I would do 1 3 2 as R CMD check works on a source dir, not a .tar.gz. Your mileage may vary and all that.
I'd say R CMD check was a final check before distribution via R CMD build. On Fri, 31 Oct 2003, Ross Boylan wrote: > On Fri, 2003-10-31 at 03:14, Prof Brian Ripley wrote: > > > But I would not be doing R CMD check until I had both installed and > > loaded the package and run a few examples. > > That's interesting; I thought R CMD check was supposed to be done before > hand. So are you saying the proper development sequence is > 1. > Do as much as you can with the basic R and C (Fortran, whatever) code to > check it's OK. > > 2. > R CMD build > test, revise > R CMD build > etc > > 3. then, when everything looks OK > R CMD check > ? > > -- Brian D. Ripley, [EMAIL PROTECTED] Professor of Applied Statistics, http://www.stats.ox.ac.uk/~ripley/ University of Oxford, Tel: +44 1865 272861 (self) 1 South Parks Road, +44 1865 272866 (PA) Oxford OX1 3TG, UK Fax: +44 1865 272595 ______________________________________________ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-help