Support for multiple versions of R about heroku-buildpack-r HOT 11 CLOSED

Great idea!

By the way, do you have a list of already compiled R binaries? Like R v3.X.X?

from heroku-buildpack-r.

If the compilation code is sufficiently well written, can't you just fork
off and build to whatever specs you like? As for checking versions, is the
amazon bucket public? (I think it is, but am not at a real computer right
now.)
On Jan 29, 2014 10:19 AM, "Benjamin Lan Sun Luk" [email protected]
wrote:

Great idea!

By the way, do you have a list of already compiled R binaries? Like R
v3.X.X?

Reply to this email directly or view it on GitHubhttps://github.com//issues/31#issuecomment-33606893
.

from heroku-buildpack-r.

@NebJ Yes, there is currently a build of R 3.0 available.

You will need to update versions in the compile script to refer to it; here and here.

The build reference version is 20131208-1524 and can be downloaded from S3 using the following Url:

https://heroku-buildpack-r.s3.amazonaws.com/R-3.0.2-binaries-20131208-1524.tar.gz

from heroku-buildpack-r.

@bwarren2 Yes, the S3 bucket is public, but only for reads.

In considering a solution to this I realized that there 3 versions in play; namely:

• the version of the build script,
• the version of R,
• and the version of the actual build-pack (I.e. the detect, compile and release scripts).

I think having multiple branches or forks to address which version of R to use may just make it unmanageable.

from heroku-buildpack-r.

@virtualstaticvoid A package I rely on, tm (term matrix), now only supports R version >= 3.0

If you recall, I use R in a multipack with node.js

BUT, to my great surprise, node no longer works after I make the upgrade. There's nothing in the build log to suggest anything is wrong.

node installs fine on its own. But when I add the R 3.0.2 build line to .buildpack and run the install, after everything completes, heroku complains that the Procfile reference to node cannot be found. (I forked your repo and made the changes you specify above, https://github.com/metalaureate/heroku-buildpack-r)

Here is the output of the git heroku push master command:

https://s3-us-west-2.amazonaws.com/umusergen/r-node-build.txt

I'm completely stumped. Any ideas much appreciated.

from heroku-buildpack-r.

@metalaureate I'm trying to replicate your issue. I suspect it may be the order in which R is included in the multi-buildpack as there is a rm on line 94 in bin/compile which deletes the temporary vendor directory during the compile process, before rebuilding it.

from heroku-buildpack-r.

Thanks! I meant to add that it didn't matter which order I put the buildpacks in.

Sent from my phone.

On Feb 17, 2014, at 2:15 PM, Chris Stefano [email protected] wrote:

@metalaureate I'm trying to replicate your issue. I suspect it may be the order in which R is included in the multi-buildpack as there is a rm on line 94 in bin/compile which deletes the temporary vendor directory during the compile process, before rebuilding it.

—
Reply to this email directly or view it on GitHub.

from heroku-buildpack-r.

@metalaureate I've updated the development branch for R 3.0.2. I tested with the packages you mentioned and it is working. Can you confirm whether it is working in the multi-buildpack scenario?

from heroku-buildpack-r.

That worked! Thanks.

from heroku-buildpack-r.

As an interim solution, you can include the following files in your application source code to override the version of R to use, and the version of the buildpack archive.

• .r-version - specify the R version to use. E.g. 3.1.2
• .r-buildpack-version - specify the buildpack archive (on S3) to use. E.g. 20150216-2120

NOTE: There is no check to see whether the 2 agree. I.e. That there is an archive for the given R version.

An example of this can be found on the cedar-14 branch under alternate-versions.

from heroku-buildpack-r.

Backported the version solution on cedar-14 branch to the cedar (master) branch.

from heroku-buildpack-r.