[R-pkg-devel] registering native routines

[Bob Rudis]

I believe you've got _some_ time. As of the changes in 3.4.0 the verbiage is:

   R CMD check --as-cran now NOTEs if the package does not register 
   its native routines or does not declare its intentions on (native) 
   symbol search. (This will become a WARNING in due course.)

And I think it's still a NOTE vs a full-on WARNING (I register all mine but can test this later).

Rcpp makes this super simple and the tools::package_native_routine_registration_skeleton() is also pretty painless as does Kevin Ushey's souretools::register_routines() (https://github.com/kevinushey/sourcetools/blob/master/R/register.R).

-boB

> On Feb 16, 2019, at 2:45 PM, Charles Geyer <charlie using stat.umn.edu> wrote:
> 
> I just noticed that R package foo in the github repo
> https://github.com/cjgeyer/foo no longer passes R CMD check --as-cran.  The
> problem seems to be that it does not register native routines and thus the
> C routines cannot be found.  It does pass R CMD check (without --as-cran).
> The version of the package that does register native routines (package
> fooRegister) in the same repo passes with or without --as-cran.  So did I
> miss the announcement?  Is registration of native routines now mandatory
> for CRAN?
> 
> Just asking because I am currently teaching about R packages in PhD level
> statistical confusing and don't want to provide erroneous info.
> 
> These packages are toy packages to introduce the class to R packages.  I
> don't actually want to put them on CRAN.
> 
> -- 
> Charles Geyer
> Professor, School of Statistics
> Resident Fellow, Minnesota Center for Philosophy of Science
> University of Minnesota
> charlie using stat.umn.edu
> 
> 	[[alternative HTML version deleted]]
> 
> ______________________________________________
> R-package-devel using r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-package-devel