Bug 16115 - R CMD check does not notice files written to forbidden locations
Summary: R CMD check does not notice files written to forbidden locations
Status: NEW
Alias: None
Product: R
Classification: Unclassified
Component: Misc (show other bugs)
Version: R 3.1.2
Hardware: All All
: P5 enhancement
Assignee: R-core
URL:
Depends on:
Blocks:
 
Reported: 2014-12-22 16:50 UTC by Andrew Ziem
Modified: 2014-12-22 16:50 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Ziem 2014-12-22 16:50:24 UTC
The CRAN policy states

"Packages should not write in the users’ home filespace, nor anywhere else on the file system apart from the R session’s temporary directory (or during installation in the location pointed to by TMPDIR: and such usage should be cleaned up). Installing into the system’s R installation (e.g., scripts to its bin directory) is not allowed. "
-- http://cran.r-project.org/web/packages/policies.html

"R CMD check" gave no indications of problems for my new package, but after submission to CRAN, the package was rejected for leaving files in /tmp.

Perhaps R CMD check could be improved by checking for these cases by either (1) monitoring file system access at a low level within R or (2) comparing the list of files in certain filespaces before and after.