On 12 October 2015 at 13:13, Charles Determan wrote: | Greetings, | | I have a package which provides headers for a C++ library (similar to the | BH package). However, the C++ library has some heavily nested components | within its' structure so when I run R CMD check I get the following NOTE: | | 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. | | Is this a major problem?
Yes. | As this is a 'NOTE' I am under the impression | that the long paths are not critical but I want to make sure. Wrong. 'BH' is called 'BH', believe it or not, to save a few letters, or else I would have a dozen or more files complain for the very same reason (and CRAN reject it for non-suitable path/filenames). Hence not 'BoostHeaders' but just 'BH'. And see the ChangeLog of BH and revel in how _each_ release has to rename one of the Runge-Kutta integration files to make the 'net' path length be suitable for R packing. There is no point in ignoring the output of R CMD check unless you _really_ know better. Dirk -- http://dirk.eddelbuettel.com | @eddelbuettel | e...@debian.org ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
