[Rd] Developer work cycle
Prof Brian Ripley
ripley at stats.ox.ac.uk
Mon Mar 26 19:23:11 CEST 2007
It depends on the change, but I never install an unreleased package into
the main library, so do not need sudo for 3). I have a 'test-library'
library that is in R_LIBS in ~/.Rprofile and I use solely for package
If this is a change to the NAMESPACE or an unexported object you do need
to re-install, but many changes can be tested via source()ing the new file
If the test suite is good enough, 'R CMD check' may do all the tests you
need without installing the test package anywhere else.
On Mon, 26 Mar 2007, "José Luis Aznarte M." wrote:
> Hi! I've been browsing through the last months' archive and I can't
> find an answer to my question, so here it is (let's hope it's not too
> I'm working on extensions of an R library, and I would be very
> surprised if everyone developing R packages is doing the following, as I do:
> 1.- Write down a modification of an R file
> 2.- Exit the current R session
> 3.- Install the package as root (sudo R CMD INSTALL...)
> 4.- Launch a new R session
> 5.- Test the change, if it does not work, go back to 1 or debug.
> 6.- Finish.
> Is this the proper (but quite awkward) way to proceed or there is an
> alternative to skip steps 2 to 4? I'm using emacs with ESS under linux.
> Thank you in advance for your time! Best regards,
> -- --
> Jose Luis Aznarte M. http://decsai.ugr.es/~jlaznarte
> Department of Computer Science and Artificial Intelligence
> Universidad de Granada Tel. +34 - 958 - 24 04 67
> GRANADA (Spain) Fax: +34 - 958 - 24 00 79
> R-devel at r-project.org mailing list
Brian D. Ripley, ripley at stats.ox.ac.uk
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
More information about the R-devel