[Rcpp-devel] package .onLoad multiple modules
baptiste.auguie at googlemail.com
Sat Jun 25 01:14:50 CEST 2011
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 release, looking forward to that.
On 25 June 2011 05:45, Dirk Eddelbuettel <edd at debian.org> wrote:
> 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'm not sure how to
> | > specify Rcpp >= 0.9.4.2 as import).
> | Version dependencies can be specified in the package's DESCRIPTION file. I have
> | this in one of my packages:
> | Depends: Rcpp (>= 0.8.6), RcppArmadillo (>= 0.2.6)
> Yes, sure, but only 'a.b.c.' versions get to CRAN, and R-Forge in all its
> wisdom does not use development versions packages hosted there. So all it
> knows is 0.9.4.
> It may be two or three more weeks til a new Rcpp release.
> Gauss once played himself in a zero-sum game and won $50.
> -- #11 at http://www.gaussfacts.com
> Rcpp-devel mailing list
> Rcpp-devel at lists.r-forge.r-project.org
More information about the Rcpp-devel