Hi,
Thanks, and indeed, given the choice r-forge always opts for CRAN
versions of packages, which is quite annoying. I removed Rcpp from
DESCRIPTION/Depends when I added it as an import(Rcpp) in NAMESPACE.
I'm not sure if both are needed/compatible.
Thanks also for the news re: the next Rcpp rele
On 24 June 2011 at 10:16, Davor Cubranic wrote:
| On June 23, 2011 08:16:59 PM baptiste auguie wrote:
| > - could we expect a CRAN release of Rcpp soon? (I am relying on this
| > new argument to loadRcppModules(), which means that my package would
| > currently fail on CRAN, and even on r-forge (I
On June 23, 2011 08:16:59 PM baptiste auguie wrote:
> - could we expect a CRAN release of Rcpp soon? (I am relying on this
> new argument to loadRcppModules(), which means that my package would
> currently fail on CRAN, and even on r-forge (I'm not sure how to
> specify Rcpp >= 0.9.4.2 as import).
