From edd at debian.org  Sat Jun 15 14:00:20 2013
From: edd at debian.org (Dirk Eddelbuettel)
Date: Sat, 15 Jun 2013 07:00:20 -0500
Subject: [Rd] R CMD INSTALL and file permission settings
In-Reply-To: <82EC6E1A-75F7-4172-968B-CA55AB102171@r-project.org>
References: <20915.23136.75704.347469@max.nulle.part>
	<20917.40985.705751.95999@stat.math.ethz.ch>
	<20923.30546.509634.752403@stat.math.ethz.ch>
	<1A628E3D-CC34-4C38-B23B-03169D3C7AD0@r-project.org>
	<20923.32408.400045.470669@max.nulle.part>
	<046C1EB4-F22D-457F-BB2C-27D666E3418F@r-project.org>
	<20923.57124.150011.263475@max.nulle.part>
	<82EC6E1A-75F7-4172-968B-CA55AB102171@r-project.org>
Message-ID: <20924.22356.973252.449984@max.nulle.part>


On 15 June 2013 at 07:47, Simon Urbanek wrote:
| Because update.packages() doesn't restore the group-writable bit. Which leads us to my point that this is not what you really want.

Ooops. I'll take another look.  

My initial patch to Martin did not have the argument to install, but simply a
fixed use of "664" and "775" modes if and only if an option() was set.  We
seem to need that in update.packages() too.

| I wasn't disputing the fact that it's great to have group-writable bit
| under control, but adding the flag to INSTALL doesn't solve the problem -
| and as you saw the result is a bit misleading in the context that it was
| discussed and thus may cause more confusion. I am arguing that the solution
| would be to (at least as default) take the directory writable bit because
| that is really what decides things anyway. You had a good point of also
| combining it with umask. 

Re umask: Users get that wrong too often too.  

I think I'd prefer to add another patch to update.packages(). 

Dirk

-- 
Dirk Eddelbuettel | edd at debian.org | http://dirk.eddelbuettel.com



[Rd] R CMD INSTALL and file permission settings
Dirk Eddelbuettel