Dear Dirk, Yes, I know, however forget for one moment R.
If I use tar independent of R it still should not create these hidden files.
BTW, do you know where these hidden files are stored on the Mac? Best regards, Christian On 09/26/15 23:01, Dirk Eddelbuettel wrote:
On 26 September 2015 at 22:41, cstrato wrote: | Dear Simon, | | Thank you very much for your help, it did solve my problems!! Great! | | I have googled COPYFILE_DISABLE and found the following site which does | explain the issue with tar on Mac OS X, see: | http://unix.stackexchange.com/questions/9665/create-tar-archive-of-a-directory-except-for-hidden-files | | Instead of doing: | $tar czf xps_1.29.2.tar.gz xps | | I did now: | $COPYFILE_DISABLE=1 tar czf xps_1.29.2.tar.gz xps | | Running: | $R CMD check xps_1.29.2.tar.gz | now leaves only '.BBSoptions' as hidden file. No, still wrong. As Simon said, we all are supposed to use 'R CMD build xps' to create the tarball. "Back in the day ..." straight tar cfz ... worked, it more or less stopped _many_ years ago. Cf TheOneManualThatMatters: 1.3.1 Checking packages ----------------------- Using 'R CMD check', the R package checker, one can test whether _source_ R packages work correctly. It can be run on one or more directories, or compressed package 'tar' archives with extension '.tar.gz', '.tgz', '.tar.bz2' or '.tar.xz'. It is strongly recommended that the final checks are run on a 'tar' archive prepared by 'R CMD build'. Ie "It is strongly recommended ... 'tar' archive prepared by 'R CMD build'. Dirk
______________________________________________ R-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-devel
