Disagree. The fallacy of one language for all and everything has already done in other camps.
Davor Cubranic @OddsAndBits
13 Nov 2015
Yes please: when your entire toolchain is #rstats, keep your build automation in R.

Nov 13, 2015 · 6:23 PM UTC

1
7
Replying to @GaborCsardi
@GaborCsardi I still disagree. IMHO we need R CMD ... patched to call roxy + compAttr. But less sure about need for outer wrapper
1
Replying to @GaborCsardi
@GaborCsardi @eddelbuettel I'm not sure I follow. R is portable and provides R CMD build, what are you looking for beyond that?
1
Replying to @GaborCsardi
@GaborCsardi @eddelbuettel @lawremi + I have talked abt stuff like this. IMO it should be a preprocessing step during INSTALL tho, not build
Replying to @GaborCsardi
@GaborCsardi @eddelbuettel Patching can definitely happen, and R CMD ... is the right place for this stuff to go.
1
Replying to @GaborCsardi
@GaborCsardi @eddelbuettel It wouldn't make much sense for both of us to do it, I'm simply saying if you're doing it, put together a patch
@groundwalkergmb @eddelbuettel I will rather put together an external build tool....
1
Replying to @eddelbuettel
@eddelbuettel what other camps? The Ruby community is very well-served by rake.