----- Original Message -----
> From: "Dirk Eddelbuettel" <e...@debian.org>
> To: "Dan Tenenbaum" <dtene...@fhcrc.org>
> Cc: "Dirk Eddelbuettel" <e...@debian.org>, "Kevin Ushey" 
> <kevinus...@gmail.com>,
> rcpp-devel@lists.r-forge.r-project.org
> Sent: Thursday, February 6, 2014 7:06:26 PM
> Subject: Re: [Rcpp-devel] Undefined Reference to typeinfo for Rcpp::RObject 
> for Rdisop on Mac after Rcpp/RcppClassic
> update
> 
> 
> On 6 February 2014 at 12:01, Dan Tenenbaum wrote:
> | If every reverse dependency of Rcpp needs a rebuild, and that
> | includes RcppClassic, does it not follow that RcppClassic needs a
> | rebuild on CRAN? Otherwise Mac or windows users without compilers
> | are out of luck.
> 
> It has always been my understanding that is what happens on Windows.
> 

What do you mean by "that"?

> But I work on Linux and I can assure you that you need to rebuild.
> 

I never doubted you on this. What I'm saying is that for people who rely on 
binary packages (mac and windows users without compilers installed), they too 
need the packages to be rebuilt against the new Rcpp, and RcppClassic has not 
been. My understanding of CRAN (which could be wrong, but this is how it works 
on Bioconductor) is that in the absence of a version bump, packages built 
during the daily builds do not propagate to the CRAN repositories. Therefore 
RcppClassic (and possibly other reverse dependencies of Rcpp) still need to be 
rebuilt, and cannot be used by Mac and Windows users unless they install from 
source and have the tools to do so, which defeats much of the purpose of having 
CRAN in the first place.

I would think that to be safe, every package that depends on Rcpp would have 
its version bumped. I did this on Bioconductor and am surprised it was not done 
on CRAN. 

Dan



> Greetings from Miami,  Dirk
> 
> --
> Dirk Eddelbuettel | e...@debian.org | http://dirk.eddelbuettel.com
> 
_______________________________________________
Rcpp-devel mailing list
Rcpp-devel@lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/rcpp-devel

Reply via email to