[R] Reading from Google Docs

Wed Jul 8 22:31:30 CEST 2009

No one really knows how many people are being
affected.

Also one can minimize the impact like this:

1. In Rtools, change find.exe to find2.exe.

2. In R, create a 'find' a variable in any script using find
and at the top check for find2 and if found set the find
variable to find2 otherwise set it to find.
Then fix the script to use the find variable instead
of find.

That would work with systems having find2 or having find
so new versions of R would work with both new and old
versions of Rtools.

The only combination that would not work would be
old versions of R with new versions of the Rtools but
that is not a likely combination and even if it does
occur it would give an error so the user would know
something is wrong which is far better than the current
situation where a silent hard-to-diagnose risk that is
entered onto your system.

On Wed, Jul 8, 2009 at 3:51 PM, Duncan Murdoch<murdoch at stats.uwo.ca> wrote:
> On 7/8/2009 3:39 PM, Gabor Grothendieck wrote:
>>
>> I understand what you wrote. Its just that I don't agree that that
>> is a reasonable solution.
>>
>> What is wanted is something that works safely out of the box,
>> not something with a built in danger that every single person
>> that uses it must fix (and know about it to fix) in order to
>> maintain the integrity of their system.
>
> As far as I know, you are the only person in the whole world who has been
> affected by this.  But fixing it would inconvenience hundreds of people, who
> would have to install a new version of Rtools, if the make system suddenly
> started looking for find2 instead of find.
>
> So it's unfortunate that Microsoft chose to use the name of the wrong Unix
> utility when they wrote find, and it's unfortunate that the first version of
> Rtools didn't fix this, but there you are:  name clashes happen, and
> sometimes you need to work around them.
>
> Duncan Murdoch
>
>>
>> On Wed, Jul 8, 2009 at 3:30 PM, Duncan Murdoch<murdoch at stats.uwo.ca>
>> wrote:
>>>
>>> On 7/8/2009 3:18 PM, Gabor Grothendieck wrote:
>>>>
>>>> To my mind its pretty serious that Rtools can make other
>>>> software not work and the importance of using the word
>>>> find in the tools is close to zero.  Most people never even
>>>> look at the scripts.
>>>
>>> You didn't read what I wrote.  It could be called anything as far as the
>>> scripts are concerned.  I explained to you how to rename it and keep them
>>> happy.
>>>
>>> Duncan Murdoch
>>>>
>>>> Why don't you just rename find.exe to find2.exe, say, in
>>>> Rtools and adjust the other files accordingly. For the small
>>>> number of people who ever look at the scripts it will be obvious
>>>> that we are dealing with a find variant and the danger and need
>>>> for kludges is eliminated.
>>>>
>>>> On Wed, Jul 8, 2009 at 12:55 PM, Duncan Murdoch<murdoch at stats.uwo.ca>
>>>> wrote:
>>>>>
>>>>> On 08/07/2009 12:04 PM, Gabor Grothendieck wrote:
>>>>>>
>>>>>> Its safer just to temporarily add it to your path.
>>>>>>
>>>>>> Unfortunately Rtools has a find command that conflicts with
>>>>>> the find command in Windows so if you add the Rtools
>>>>>> bin directory to your path permanently then you could
>>>>>> find other programs stop working.  That actually happened
>>>>>> to me once and it took the longest time until I discovered
>>>>>> that Rtools was the culprit.
>>>>>
>>>>> That's true, but there is a workaround: you can manually rename the
>>>>> find.exe
>>>>> in Rtools, and adjust the entry in one of the R makefiles (MkRules),
>>>>> and
>>>>> it
>>>>> will use the new name instead of "find".  The reason you might not want
>>>>> to
>>>>> do this is you might expect find to act the way it does on Unix:  the
>>>>> Rtools
>>>>> basically try to make Windows look a little bit like Unix.
>>>>>
>>>>> Duncan Murdoch
>>>>>
>>>>>>
>>>>>> If you follow the advice I gave you normally won't have
>>>>>> that problem.
>>>>>>
>>>>>> On Wed, Jul 8, 2009 at 11:21 AM, Duncan Murdoch<murdoch at stats.uwo.ca>
>>>>>> wrote:
>>>>>>>
>>>>>>> On 08/07/2009 10:13 AM, Farrel Buchinsky wrote:
>>>>>>>>
>>>>>>>> Forgive my naivte, but how do I make windows find tar. In other
>>>>>>>> words
>>>>>>>> from
>>>>>>>> where do I issue the command and what is the command.
>>>>>>>
>>>>>>> You need to install the toolset, and let the installer set your path.
>>>>>>>
>>>>>>> Duncan Murdoch
>>>>>>>
>>>>>>>> Farrel Buchinsky
>>>>>>>> Google Voice Tel: (412) 567-7870
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> On Wed, Jul 8, 2009 at 10:09, Duncan Murdoch <murdoch at stats.uwo.ca>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> On 08/07/2009 10:02 AM, Farrel Buchinsky wrote:
>>>>>>>>>
>>>>>>>>>> I  have previously read "R Installation and Administration". I
>>>>>>>>>> read
>>>>>>>>>> it
>>>>>>>>>> again. It does not help me
>>>>>>>>>> The relevant paragraph is below. But I need lower level
>>>>>>>>>> instructions.
>>>>>>>>>> Where
>>>>>>>>>> can I find them.
>>>>>>>>>>
>>>>>>>>> Follow the link.  If Windows can't find tar, your toolset is
>>>>>>>>> installed
>>>>>>>>> incorrectly.
>>>>>>>>>
>>>>>>>>> Duncan Murdoch
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>> R CMD INSTALL works in Windows to install source packages if you
>>>>>>>>>> have
>>>>>>>>>> the
>>>>>>>>>> source-code package files (option “Source Package Installation
>>>>>>>>>> Files”
>>>>>>>>>> in
>>>>>>>>>> the
>>>>>>>>>> installer) and toolset (see The Windows
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> toolset<file:///C:/Program%20Files/R/R-2.9.1/doc/manual/R-admin.html#The-Windows-toolset>)
>>>>>>>>>>
>>>>>>>>>> installed. Installation of binary packages must be done by
>>>>>>>>>> install.packages
>>>>>>>>>> . R CMD INSTALL --help will tell you the current options under
>>>>>>>>>> Windows
>>>>>>>>>> (which differ from those on a Unix-alike): in particular there is
>>>>>>>>>> a
>>>>>>>>>> choice
>>>>>>>>>> of the types of documentation to be installed.
>>>>>>>>>> Farrel Buchinsky
>>>>>>>>>> Google Voice Tel: (412) 567-7870
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> 2009/6/19 Uwe Ligges <ligges at statistik.tu-dortmund.de>
>>>>>>>>>>
>>>>>>>>>>  See the manual "R Installation and Administration" for
>>>>>>>>>> information
>>>>>>>>>> on
>>>>>>>>>> how
>>>>>>>>>>>
>>>>>>>>>>> to install source packages on Windows.
>>>>>>>>>>>
>>>>>>>>>>> Uwe Ligges
>>>>>>>>>>>
>>>>>>>>>>> Farrel Buchinsky wrote:
>>>>>>>>>>>
>>>>>>>>>>>  After issuing tar xvfz RgoogleDocs_0.2.2-src.tar.gzI am getting
>>>>>>>>>>> an
>>>>>>>>>>> error
>>>>>>>>>>>>
>>>>>>>>>>>> message
>>>>>>>>>>>> 'tar' is not recongnized as an internal or external command,
>>>>>>>>>>>> operable
>>>>>>>>>>>> program or batch file.
>>>>>>>>>>>>
>>>>>>>>>>>> Should I use my 7-zip to open up the archive?
>>>>>>>>>>>> Where should I be doing this? For instance can I do it all in my
>>>>>>>>>>>> download directory or should I do it in C:\Program
>>>>>>>>>>>> Files\R\R-2.9.0\library or should I manually create C:\Program
>>>>>>>>>>>> Files\R\R-2.9.0\library\RGoogleDocs and do it all there or will
>>>>>>>>>>>> the
>>>>>>>>>>>> Rcmd
>>>>>>>>>>>> INSTALL RGoogleDocs_0.2-2.tar.gz command do that for me.
>>>>>>>>>>>>
>>>>>>>>>>>> Yes, you assumed correctly. I am using Windows XP.
>>>>>>>>>>>> Farrel Buchinsky
>>>>>>>>>>>> Google Voice Tel: (412) 567-7870
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> On Thu, Jun 18, 2009 at 20:17, Gabor Grothendieck
>>>>>>>>>>>> <ggrothendieck at gmail.com>wrote:
>>>>>>>>>>>>
>>>>>>>>>>>>  I have haven't neen following this thread but:
>>>>>>>>>>>>
>>>>>>>>>>>>> 1. if RGoogleDocs_0.2-2.tar.gz is a source distribution (as
>>>>>>>>>>>>> opposed to built source) then the first line renames it so
>>>>>>>>>>>>> that its not the same name as the built file about to be
>>>>>>>>>>>>> created.
>>>>>>>>>>>>> The second line detars it into the RGoogleDocs directory.  The
>>>>>>>>>>>>> third
>>>>>>>>>>>>> builds
>>>>>>>>>>>>> the built source file, RGoogleDocs_0.2-2.tar.gz.  The fourth
>>>>>>>>>>>>> installs the built source file into R.  I've assumed Windows.
>>>>>>>>>>>>> If you are on Linux replace rename with mv.
>>>>>>>>>>>>>
>>>>>>>>>>>>> rename RGoogleDocs_0.2-2.tar.gz RgoogleDocs_0.2.2-src.tar.gz
>>>>>>>>>>>>> tar xvfz RgoogleDocs_0.2.2-src.tar.gz
>>>>>>>>>>>>> Rcmd build RGoogleDocs
>>>>>>>>>>>>> Rcmd INSTALL RGoogleDocs_0.2-2.tar.gz
>>>>>>>>>>>>>
>>>>>>>>>>>>> or
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2. if RGoogleDocs_0.2-2.tar.gz is already a built source file
>>>>>>>>>>>>> then
>>>>>>>>>>>>> you
>>>>>>>>>>>>> can just issue the last of the above lines and don't need
>>>>>>>>>>>>> the others.
>>>>>>>>>>>>>
>>>>>>>>>>>>> On Thu, Jun 18, 2009 at 7:52 PM, Farrel
>>>>>>>>>>>>> Buchinsky<fjbuch at gmail.com>
>>>>>>>>>>>>> wrote:
>>>>>>>>>>>>>
>>>>>>>>>>>>>  What do you mean by "cd the.directory.containing.RGoogleDocs"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Do you mean the directory where I downloaded the
>>>>>>>>>>>>>> RGoogleDocs_0.2-2.tar.gz
>>>>>>>>>>>>>> to? Or do you mean that I must create a directory called
>>>>>>>>>>>>>> RGoogleDocs
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  under
>>>>>>>>>>>>>
>>>>>>>>>>>>>  Library and then change to that directory?
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Farrel Buchinsky
>>>>>>>>>>>>>> Google Voice Tel: (412) 567-7870
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Mon, Mar 2, 2009 at 22:16, Gabor Grothendieck <
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  ggrothendieck at gmail.com>
>>>>>>>>>>>>>
>>>>>>>>>>>>>  wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>>  Finally enter into the Windows console:
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> cd the.directory.containing.RGoogleDocs
>>>>>>>>>>>>>>> Rcmd build RGoogleDocs
>>>>>>>>>>>>>>> Rcmd INSTALL RGoogleDocs_1.0.0.tar.gz
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>> except replace RGoogleDocs_1.0.0.tar.gz with the filename
>>>>>>>>>>>>>>> created by the build.
>>>>>>>>>>>>>>>
>>>>>>>>>>>>>>>    [[alternative HTML version deleted]]
>>>>>>>>>>>>
>>>>>>>>>>>> ______________________________________________
>>>>>>>>>>>> R-help at r-project.org mailing list
>>>>>>>>>>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>>>>>>>>>>> PLEASE do read the posting guide
>>>>>>>>>>>> http://www.R-project.org/posting-guide.html
>>>>>>>>>>>> and provide commented, minimal, self-contained, reproducible
>>>>>>>>>>>> code.
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>    [[alternative HTML version deleted]]
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>>>
>>>>>>>>>> ______________________________________________
>>>>>>>>>> R-help at r-project.org mailing list
>>>>>>>>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>>>>>>>>> PLEASE do read the posting guide
>>>>>>>>>> http://www.R-project.org/posting-guide.html
>>>>>>>>>> and provide commented, minimal, self-contained, reproducible code.
>>>>>>>>>>
>>>>>>>>     [[alternative HTML version deleted]]
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> ------------------------------------------------------------------------
>>>>>>>>
>>>>>>>> ______________________________________________
>>>>>>>> R-help at r-project.org mailing list
>>>>>>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>>>>>>> PLEASE do read the posting guide
>>>>>>>> http://www.R-project.org/posting-guide.html
>>>>>>>> and provide commented, minimal, self-contained, reproducible code.
>>>>>>>
>>>>>>> ______________________________________________
>>>>>>> R-help at r-project.org mailing list
>>>>>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>>>>>> PLEASE do read the posting guide
>>>>>>> http://www.R-project.org/posting-guide.html
>>>>>>> and provide commented, minimal, self-contained, reproducible code.
>>>>>>>
>>>>>>
>>>>>> ______________________________________________
>>>>>> R-help at r-project.org mailing list
>>>>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>>>>> PLEASE do read the posting guide
>>>>>> http://www.R-project.org/posting-guide.html
>>>>>> and provide commented, minimal, self-contained, reproducible code.
>>>>>
>>>>>
>>>>
>>>> ______________________________________________
>>>> R-help at r-project.org mailing list
>>>> https://stat.ethz.ch/mailman/listinfo/r-help
>>>> PLEASE do read the posting guide
>>>> http://www.R-project.org/posting-guide.html
>>>> and provide commented, minimal, self-contained, reproducible code.
>>>
>>>
>
>