Check results for 'ruijter' (original) (raw)

• using R version 4.3.1 (2023-06-16)
• using platform: aarch64-apple-darwin20 (64-bit)
• R was compiled by Apple clang version 14.0.0 (clang-1400.0.29.202) GNU Fortran (GCC) 12.2.0
• running under: macOS Ventura 13.4
• using session charset: UTF-8
• checking for file ‘ruijter/DESCRIPTION’ ... OK
• checking extension type ... Package
• this is package ‘ruijter’ version ‘0.1.3’
• package encoding: UTF-8
• 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 ‘ruijter’ can be installed ... [2s/2s] OK See the install log for details.
• 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 ... [0s/0s] OK
• checking whether the package can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the package can be unloaded cleanly ... [0s/0s] OK
• checking whether the namespace can be loaded with stated dependencies ... [0s/0s] OK
• checking whether the namespace can be unloaded cleanly ... [0s/0s] OK
• checking loading without being on the library search path ... [0s/0s] 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 ... [1s/1s] OK
• checking Rd files ... [0s/0s] 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 contents of ‘data’ directory ... OK
• checking data for non-ASCII characters ... [0s/0s] OK
• checking LazyData ... OK
• checking data for ASCII and uncompressed saves ... OK
• checking examples ... NONE
• checking PDF version of manual ... [3s/4s] OK
• DONE Status: OK
• using check arguments '--no-clean-on-error '