Reincluding ext.js gives a NOTE due to path lengths exceeding 100 bytes... As it is a NOTE this may not prevent publication on CRAN.
The WARNINGS are about code documentation mismatches and usage sections, I wonder if they are produced during the Roxygen runs?
Here is the check log (took out most of the path length warnings)
- using log directory ‘/home/ranke/git/gWidgetsWWW2.Rcheck’
- using R version 3.0.2 (2013-09-25)
- using platform: x86_64-pc-linux-gnu (64-bit)
- using session charset: UTF-8
- checking for file ‘gWidgetsWWW2/DESCRIPTION’ ... OK
- this is package ‘gWidgetsWWW2’ version ‘0.4-0’
- 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 ... NOTE
Found the following hidden files and directories:
inst/base/javascript/ext-4-2.1/packages/ext-locale/.sencha
inst/base/javascript/ext-4-2.1/packages/ext-theme-access/.sencha
inst/base/javascript/ext-4-2.1/packages/ext-theme-base/.sencha
inst/base/javascript/ext-4-2.1/packages/ext-theme-classic-sandbox/.sencha
inst/base/javascript/ext-4-2.1/packages/ext-theme-classic/.sencha
inst/base/javascript/ext-4-2.1/packages/ext-theme-gray/.sencha
inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/.sencha
inst/base/javascript/ext-4-2.1/packages/ext-theme-neutral/.sencha
These were most likely included in error. See section ‘Package
structure’ in the ‘Writing R Extensions’ manual.
- checking for portable file names ... NOTE
Found the following non-portable file paths:
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-access/.sencha/package/build.properties
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-access/.sencha/package/testing.properties
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-access/build/ext-theme-access-all-debug.scss
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-access/build/ext-theme-access-all-rtl-debug.scss
...
removed about 5000 lines
...
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/build/resources/images/loadmask
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/build/resources/images/panel-header
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/build/resources/images/tab-bar
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/build/resources/images/toolbar
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/build/resources/images/util/splitter
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/build/resources/images/window-header
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/packages/ext-theme-neptune/resources/images/util/splitter
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/resources/ext-theme-access/images/grid-row-editor-buttons
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/resources/ext-theme-classic-sandbox/images/grid-row-editor-buttons
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/resources/ext-theme-classic/images/grid-row-editor-buttons
gWidgetsWWW2/inst/base/javascript/ext-4-2.1/resources/ext-theme-neptune/images/grid-row-editor-buttons
Tarballs are only required to store paths of up to 100 bytes and cannot
store those of more than 256 bytes, with restrictions including to 100
bytes for the final component.
See section ‘Package structure’ in the ‘Writing R Extensions’ manual.
- checking for sufficient/correct file permissions ... OK
- checking whether package ‘gWidgetsWWW2’ can be installed ... OK
- checking installed package size ... NOTE
installed size is 94.6Mb
sub-directories of 1Mb or more:
R 1.2Mb
base 92.5Mb
- 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 ... NOTE
Packages in Depends field not imported from:
‘RJSONIO’ ‘digest’ ‘memoise’ ‘whisker’
These packages needs to imported from for the case when
this namespace is loaded but not attached.
‘:::’ call which should be ‘::’: ‘Rook:::Utils’
See the note in ?:::
about the use of this operator.
See the information on DESCRIPTION files in the chapter ‘Creating R
packages’ of the ‘Writing R Extensions’ manual.
- 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 ... WARNING
Codoc mismatches from documentation object '[<-.GComponent':
[<-.GComponent
Code: function(x, i, j, ..., value)
Docs: function(x, i, j, ..., value, value)
Codoc mismatches from documentation object 'editable<-':
editable<-
Code: function(x, ..., value)
Docs: function(x, ..., value, value)
editable<-.GComponent
Code: function(x, ..., value)
Docs: function(x, ..., value, value)
Codoc mismatches from documentation object 'enabled<-':
enabled<-
Code: function(x, value)
Docs: function(x, value, value)
enabled<-.GComponent
Code: function(x, value)
Docs: function(x, value, value)
Codoc mismatches from documentation object 'focus<-':
focus<-
Code: function(x, value)
Docs: function(x, value, value)
focus<-.default
Code: function(x, value)
Docs: function(x, value, value)
Codoc mismatches from documentation object 'font<-':
font<-
Code: function(x, value)
Docs: function(x, value, value)
font<-.GComponent
Code: function(x, value)
Docs: function(x, value, value)
Codoc mismatches from documentation object 'names<-.GComponent':
names<-.GComponent
Code: function(x, value)
Docs: function(x, value, value)
Codoc mismatches from documentation object 'size<-':
size<-
Code: function(x, ..., value)
Docs: function(x, ..., value, value)
size<-.GComponent
Code: function(x, ..., value)
Docs: function(x, ..., value, value)
Codoc mismatches from documentation object 'svalue<-':
svalue.GComponent
Code: function(x, index = NULL, drop = NULL, ...)
Docs: function(x, index = NULL, ..., value)
Argument names in code not in docs:
drop
Argument names in docs not in code:
value
Mismatches in argument names:
Position: 3 Code: drop Docs: ...
Position: 4 Code: ... Docs: value
svalue<-
Code: function(x, index = NULL, ..., value)
Docs: function(x, index = NULL, ..., value, value)
Codoc mismatches from documentation object 'tag<-':
tag<-
Code: function(x, key, value)
Docs: function(x, key, value, value)
tag<-.GComponent
Code: function(x, key, value)
Docs: function(x, key, value, value)
Codoc mismatches from documentation object 'tooltip<-':
tooltip<-
Code: function(x, value)
Docs: function(x, value, value)
tooltip<-.default
Code: function(x, value)
Docs: function(x, value, value)
Codoc mismatches from documentation object 'visible<-':
visible<-
Code: function(x, value)
Docs: function(x, value, value)
visible<-.GComponent
Code: function(x, value)
Docs: function(x, value, value)
- checking Rd \usage sections ... WARNING
Undocumented arguments in documentation object 'Array-class'
‘...’
Objects in \usage without \alias in documentation object 'Array-class':
‘Array’
Undocumented arguments in documentation object 'Authenticator-class'
‘...’
Objects in \usage without \alias in documentation object 'Authenticator-class':
‘Authenticator’
Undocumented arguments in documentation object 'ExtArgs-class'
‘...’
Objects in \usage without \alias in documentation object 'ExtArgs-class':
‘ExtArgs’
Undocumented arguments in documentation object 'GContainer'
‘...’
Undocumented arguments in documentation object 'GDialog'
‘...’
Undocumented arguments in documentation object 'GGoogleMapsObject'
‘...’
Undocumented arguments in documentation object 'GGoogleMapsPolygon'
‘...’
Undocumented arguments in documentation object 'GWidgetArrayProxy'
‘...’
Undocumented arguments in documentation object 'GWidgetArrayStore'
‘...’
Undocumented arguments in documentation object 'GWidgetHTMLProxy'
‘...’
Undocumented arguments in documentation object 'GWidgetProxy'
‘...’
Undocumented arguments in documentation object 'GWidgetStore'
‘...’
Undocumented arguments in documentation object 'GWidgetText'
‘...’
Undocumented arguments in documentation object 'GWidgetsTopLevel-class'
‘...’
Objects in \usage without \alias in documentation object 'GWidgetsTopLevel-class':
‘GWidgetsTopLevel’
Undocumented arguments in documentation object 'JsonRPCObject-class'
‘...’
Objects in \usage without \alias in documentation object 'JsonRPCObject-class':
‘JsonRPCObject’
Undocumented arguments in documentation object 'JsonRPCServer-class'
‘...’
Objects in \usage without \alias in documentation object 'JsonRPCServer-class':
‘JsonRPCServer’
Undocumented arguments in documentation object 'gWidgetsWWW2-package'
‘...’
Undocumented arguments in documentation object 'GAction'
‘...’
Undocumented arguments in documentation object 'GGroup'
‘...’
Undocumented arguments in documentation object 'gmenu-class'
‘...’
Objects in \usage without \alias in documentation object 'gmenu-class':
‘GMenu’
Undocumented arguments in documentation object 'gstatusbar-class'
‘...’
Objects in \usage without \alias in documentation object 'gstatusbar-class':
‘GStatusbar’
Undocumented arguments in documentation object 'gsvg-class'
‘...’
Objects in \usage without \alias in documentation object 'gsvg-class':
‘GSvg’
Objects in \usage without \alias in documentation object 'svalue<-':
‘svalue.GComponent’
Bad \usage lines found in documentation object 'svalue<-':
<- value
Functions with \usage entries need to have the appropriate \alias
entries, and all their arguments documented.
The \usage entries must correspond to syntactically valid R code.
See the chapter ‘Writing R documentation files’ in the ‘Writing R
Extensions’ manual.
- checking Rd contents ... OK
- checking for unstated dependencies in examples ... OK
- checking sizes of PDF files under ‘inst/doc’ ... OK
- checking installed files from ‘inst/doc’ ... OK
- checking files in ‘vignettes’ ... OK
- checking examples ... OK
- checking for unstated dependencies in vignettes ... OK
- checking package vignettes in ‘inst/doc’ ... OK
- checking running R code from vignettes ... OK
- checking re-building of vignette outputs ... OK
- checking PDF version of manual ... OK
WARNING: There were 2 warnings.
NOTE: There were 4 notes.