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 compile library objects, right?

It would still be nice to have devel binary core packages, even if CRAN
page states:

"CRAN itself does no longer mirror source snapshots (as of 2001-11-14),
because it makes only limited sense to propagate archives that change on a
daily basis through a network of mirror sites. When a snapshot reaches one
of the final nodes in the mirroring process, there are already 2 newer
versions available at the orginal sites."

As for package checking is concerned, getting an update of R-devel that is
2 versions late would be perfectly fine, wouldn't it?
When compiling from source, R and R-devel coexist happily if one specifies
an installation prefix other than the default. What other conflict could
happen?

Renaud



2013/2/27 Dirk Eddelbuettel <edd@debian.org>

>
> 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 :-/
>
> Until the package "timeMachine" appears on CRAN, I do keep an svn checkout
> which I update about once a week.  I have a little build script which I
> posted once and which I'd be happy to send to you but I can't show it in
> public for risk of ex-communication as it builds in the very verboten place
> (and no, I've never been bitten but yes I do make distclean too).
>
> Dirk
>
> --
> Dirk Eddelbuettel | edd@debian.org | http://dirk.eddelbuettel.com
>
>

	[[alternative HTML version deleted]]

