On Fri, 2003-10-31 at 13:29, Prof Brian Ripley wrote: > 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'm not following something. 1 3 2 was what I was doing. I thought you said (below on Fri) that you'd do 2, then 3. I may be misunderstanding what the phrase "installed and loaded the package" means. I thought installing and loading it referred to doing an R CMD build to make the package, and then R CMD INSTALL on the result.
> > 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 > > ? > > > > -- Ross Boylan wk: (415) 502-4031 530 Parnassus Avenue (Library) rm 115-4 [EMAIL PROTECTED] Dept of Epidemiology and Biostatistics fax: (415) 476-9856 University of California, San Francisco San Francisco, CA 94143-0840 hm: (415) 550-1062 ______________________________________________ [EMAIL PROTECTED] mailing list https://www.stat.math.ethz.ch/mailman/listinfo/r-help
