From murdoch.duncan at gmail.com  Mon Apr 22 16:27:17 2013
From: murdoch.duncan at gmail.com (Duncan Murdoch)
Date: Mon, 22 Apr 2013 10:27:17 -0400
Subject: [Rd] R 3.0, Rtools3.0,l Windows7 64-bit, and permission agony
In-Reply-To: <CABdHhvG2hz+foxwePt1sv6CCRYxg2OJKUDxbYo6r67qpYF1=Sw@mail.gmail.com>
References: <5171B903.50401@gmail.com> <5172B8FC.6010004@gmail.com>
	<CAP01uRmCLc67t=t0qeUjsj4QsTVN1vp9VZnWH6iNCYpzjCXJGQ@mail.gmail.com>
	<5172D661.4000703@gmail.com> <5172D84F.3060801@gmail.com>
	<5172DC98.8040308@gmail.com> <517319E5.4040800@gmail.com>
	<CABdHhvFSnwMxx7kDs7vw6LvMTwEzw_X_6=WBQOf3FHqGM2piiQ@mail.gmail.com>
	<CAP01uRkq2PXwrQfN5MAjWuE02QtQxVu8raa2uhW4rOi9BGvuzg@mail.gmail.com>
	<CABdHhvFsiuTmnW8So3TdoKcDVsqtM0sO18NivEjr3JfSG9Bcfg@mail.gmail.com>
	<CAP01uRnP1CJSbtYJHEB3X8GY5CfcbfCgZ=R78SwEuAesYOYMUQ@mail.gmail.com>
	<CABdHhvGQYGa2uJSMFYvL=Ckm=cD27ZAGDQqXPMuhuFr3dRsmUg@mail.gmail.com>
	<CAP01uRmfY1dqk_-8Cq0GodNuFGCGMGcUU6BhBwrNB7hH6bwHeA@mail.gmail.com>
	<CABdHhvHfW6r3fjJeuGUjyRNq0VOBr2YFDiHnu_jmqu6NE7F_WA@mail.gmail.com>
	<CAP01uRnLdB6MA=pbW8C6TJCXFGeSso=HssGNq=GtGKcB7BiK9Q@mail.gmail.com>
	<CAFDcVCRjpWU=PRAC7BBscAiBm1PFb9tK4BWn3NQjrP6PGo=Nhw@mail.gmail.com>
	<CABdHhvG2hz+foxwePt1sv6CCRYxg2OJKUDxbYo6r67qpYF1=Sw@mail.gmail.com>
Message-ID: <517548C5.6050203@gmail.com>

On 21/04/2013 6:57 PM, Hadley Wickham wrote:
> > PS. Hadley, is this what you meant when you wrote "Better solutions
> > (e.g. Rstudio and devtools) temporarily set the path on when you're
> > calling R CMD *.", or those approaches are only when you call 'R CMD'
> > from the R prompt?  I believe the latter, but I just want to make sure
> > I didn't miss something.
>
> Well both devtools and RStudio allow you to do package development
> without leaving R, so neither do anything to your path when you're not
> using them.
>
> In teaching windows users to develop R packages, I found the use of
> the command line to be a substantial road-block, and if you can
> develop packages without leaving R, why not?

The idea of temporary additions to the path during the 
INSTALL/build/check code sounds reasonable.  R could probably do it more 
accurately than devtools or RStudio can (since we know the requirements, 
and you have to guess at them), but could hopefully do it in a way that 
isn't incompatible with those.

The code called by install.packages() and related functions within R is 
essentially the same code as called by R CMD INSTALL etc from the 
command line, so this would help both cases.

Duncan Murdoch



[Rd] R 3.0, Rtools3.0,l Windows7 64-bit, and permission agony
Duncan Murdoch