• using R version 2.14.1 (2011-12-22)
• using platform: i686-pc-linux-gnu (32-bit)
• using session charset: UTF-8
• using option ‘--no-vignettes’
• checking for file ‘CPE/DESCRIPTION’ ... OK
• this is package ‘CPE’ version ‘1.4.2’
• checking package dependencies ... OK
• checking if this is a source package ... OK
• checking if there is a namespace ... NOTE
  As from R 2.14.0 all packages need a namespace.
  One will be generated on installation, but it is better to handcraft a
  NAMESPACE file: R CMD build will produce a suitable starting point.
• checking for executable files ... OK
• checking whether package ‘CPE’ can be installed ... OK
• checking installed package size ... OK
• checking package directory ... OK
• checking for portable file names ... OK
• checking for sufficient/correct file permissions ... OK
• checking DESCRIPTION meta-information ... OK
• checking top-level 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 for unstated 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 ... NOTE
  File ‘CPE/R/zzz.R’:
  .First.lib calls:
  cat("CPE 1.4.2 loaded\n")
  
  Package startup functions should use ‘packageStartupMessage’ to
  generate messages.
  See section ‘Good practice’ in ?.onAttach.
  
• 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 C/C++/Fortran sources/headers ... OK
• checking line endings in Makefiles ... OK
• checking for portable compilation flags in Makevars ... OK
• checking for portable use of $(BLAS_LIBS) and $(LAPACK_LIBS) ... OK
• checking compiled code ... OK
• checking examples ... OK
• checking PDF version of manual ... OK