>
> This is actually a pretty big peeve of mine. "Program Files" is where
> programs are *supposed* to reside on Windows.
>
PS -- Microsoft's reasoning is explained in "Why do program files go into
the Program Files directory?"
https://blogs.msdn.microsoft.com/oldnewthing/20120307-00/?p=8153
Does Windows allow creating a symlink to "C:/Program Files"?
If so, R could install into the conventional Windows location, but use the
symlink for all its access, yes?
Windows 10 command = mklink
On Fri, Dec 8, 2017 at 11:14 AM, Zach Bjornson wrote:
> Thanks for fixing
Thanks for fixing this!
For what it's worth, the Windows installers for other programming
language runtimes often install outside of Program Files, so at least
there is 'prior art' to motivate having R install directly into the
root of the home drive:
This is actually a pretty big peeve of
On 8 December 2017 at 08:52, Kevin Ushey wrote:
| For what it's worth, the Windows installers for other programming
| language runtimes often install outside of Program Files, so at least
| there is 'prior art' to motivate having R install directly into the
| root of the home drive:
|
| -
For what it's worth, the Windows installers for other programming
language runtimes often install outside of Program Files, so at least
there is 'prior art' to motivate having R install directly into the
root of the home drive:
- ActiveState Perl installs directly C:/Perl;
- Python
On 12/07/2017 06:15 PM, Dirk Eddelbuettel wrote:
On 7 December 2017 at 17:56, Tomas Kalibera wrote:
|
| An update on this. Writing R Extensions does not recommend to have a
| space character in R_HOME. This means that on Windows one either should
| have SFN enabled (which is still the common