CRAN upload

[eddelbuettel]

@nlarusstone @fingoldin I cleaned up one or two things, renamed the package to be named 'corels' as well as moved it here. The possible Corels reading bug identified in December is still present, but the package is otherwise 'clean'.

So I suggest to upload to CRAN in a few days.

Let me know your thoughts or remind me of open issues with the R package I may have forgotten.

[eddelbuettel]

Check log just in case:

edd@rob:~/git/rcppcorels(master)$ R CMD check corels_0.0.2.tar.gz 
* using log directory ‘/home/edd/git/rcppcorels/corels.Rcheck’
* using R version 4.0.0 (2020-04-24)
* using platform: x86_64-pc-linux-gnu (64-bit)
* using session charset: UTF-8
* checking for file ‘corels/DESCRIPTION’ ... OK
* checking extension type ... Package
* this is package ‘corels’ version ‘0.0.2’
* checking package namespace information ... OK
* checking package dependencies ... OK
* checking if this is a source package ... OK
* checking if there is a namespace ... OK
* checking for executable files ... OK
* checking for hidden files and directories ... OK
* checking for portable file names ... OK
* checking for sufficient/correct file permissions ... OK
* checking whether package ‘corels’ can be installed ... OK
* checking installed package size ... OK
* checking package directory ... OK
* checking DESCRIPTION meta-information ... OK
* checking top-level files ... OK
* checking for left-over files ... OK
* checking index information ... OK
* checking package subdirectories ... OK
* checking R files for non-ASCII characters ... OK
* checking R files for syntax errors ... OK
* checking whether the package can be loaded ... OK
* checking whether the package can be loaded with stated dependencies ... OK
* checking whether the package can be unloaded cleanly ... OK
* checking whether the namespace can be loaded with stated dependencies ... OK
* checking whether the namespace can be unloaded cleanly ... OK
* checking loading without being on the library search path ... OK
* checking dependencies in R code ... OK
* checking S3 generic/method consistency ... OK
* checking replacement functions ... OK
* checking foreign function calls ... OK
* checking R code for possible problems ... OK
* checking Rd files ... OK
* checking Rd metadata ... OK
* checking Rd cross-references ... OK
* checking for missing documentation entries ... OK
* checking for code/documentation mismatches ... OK
* checking Rd \usage sections ... OK
* checking Rd contents ... OK
* checking for unstated dependencies in examples ... OK
* checking line endings in shell scripts ... OK
* checking line endings in C/C++/Fortran sources/headers ... OK
* checking line endings in Makefiles ... OK
* checking compilation flags in Makevars ... OK
* checking for GNU extensions in Makefiles ... OK
* checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
* checking use of PKG_*FLAGS in Makefiles ... OK
* checking compilation flags used ... OK
* checking compiled code ... OK
* checking examples ... OK
* checking PDF version of manual ... OK
* DONE

Status: OK

edd@rob:~/git/rcppcorels(master)$ 

[nlarusstone]

Sounds good to me -- looking forward to getting it on CRAN.

[eddelbuettel]

On its way. It has been submitted, we will see if any required changes are requested.

[eddelbuettel]

And on CRAN now, so closing the ticket.