On 27/02/2013, at 18:08 PM, Dirk Eddelbuettel wrote:
>
> On 27 February 2013 at 17:16, Renaud wrote:
> | Hi,
> |
> | thanks for the responses.
> | Dirk I found the script you posted once. Can anyone send me a link to the
> | "beaten to death post"?
>
> Those were Simon's words, not mine, but
On 27 February 2013 at 17:16, Renaud wrote:
| Hi,
|
| thanks for the responses.
| Dirk I found the script you posted once. Can anyone send me a link to the
| "beaten to death post"?
Those were Simon's words, not mine, but I think he referred to the long-ish
and painful thread here:
http://t
Hi,
thanks for the responses.
Dirk I found the script you posted once. Can anyone send me a link to the
"beaten to death post"?
I am fine with these approaches and kind of already follow them.
I imagine that after an R-devel update you have to re-install all the
contrib packages that need to comp
On 27 February 2013 at 12:08, Renaud wrote:
| is checking out R SVN trunk the recommended way to keep up to date with
| R-devel and check packages with the latest version?
In theory.
In practice you need a time machine as I just something rejected for a test
that did not exist when I submitted :
On Feb 27, 2013, at 5:08 AM, Renaud wrote:
> Hi,
>
> is checking out R SVN trunk the recommended way to keep up to date with
> R-devel and check packages with the latest version?
>
> My objective is to be able to have both R and R-devel versions
> installed/working and up to date.
> R-devel bina
Hi,
is checking out R SVN trunk the recommended way to keep up to date with
R-devel and check packages with the latest version?
My objective is to be able to have both R and R-devel versions
installed/working and up to date.
R-devel binaries would be available as symlinks in my home directory so
