John,
Taking this off-list. I suspect this is pretty much unique to you, but
we will see. I am about to add a para to 'Writing R Extensions' along
the lines of
'Where a non-POSIX file system is in use which does not utilize execute
permissions, some care is needed with permissions. This a
Dear Brian,
I hope that I can clarify the issue and not confuse it further. I apologize if
I was less than clear.
I originally built the tarball for the sem package on my Windows 7 system using
"R CMD build" via RStudio with R 3.0.0. Both my Windows 7 system and the
Windows 8 system that I sub
On 13-04-15 03:19 PM, Prof Brian Ripley wrote:
On 15/04/2013 14:11, John Fox wrote:
Dear Brian,
On Mon, 15 Apr 2013 06:56:26 +0100
Prof Brian Ripley wrote:
POSIX-style execute permission isn't a Windows concept, so it was
fortuitous this ever worked. One possibility is that Cygwin was
in
On 15/04/2013 14:11, John Fox wrote:
Dear Brian,
On Mon, 15 Apr 2013 06:56:26 +0100
Prof Brian Ripley wrote:
POSIX-style execute permission isn't a Windows concept, so it was fortuitous
this ever worked. One possibility is that Cygwin was involved, and a Cygwin
emulation got set when tar
Dear Brian,
On Mon, 15 Apr 2013 06:56:26 +0100
Prof Brian Ripley wrote:
> POSIX-style execute permission isn't a Windows concept, so it was fortuitous
> this ever worked. One possibility is that Cygwin was involved, and a Cygwin
> emulation got set when tar unpacked the file and converted bac
POSIX-style execute permission isn't a Windows concept, so it was
fortuitous this ever worked. One possibility is that Cygwin was
involved, and a Cygwin emulation got set when tar unpacked the file and
converted back to the tar representation when Cygwin tar produced the
tarball. (The tar in R
