Thanks. I am old and slow and often overlook things, but I don’t see the tools directory in that file that you are pointing to, which would be consistent with the error message you are getting because that is where the file being name reside. So you can either add that to the .Rbuildignore. or remove it if not needed.
HTH, -Roy > On Jul 5, 2025, at 2:38 PM, Reed A. Cartwright <racartwri...@gmail.com> wrote: > > Dear Roy, > > I think you might have looked at the wrong file. My .Rbuildignore is > here https://github.com/reedacartwright/ironseed/blob/main/.Rbuildignore. > > Thanks for looking, > > Cheers. > > On Sat, Jul 5, 2025 at 2:33 PM Roy Mendelssohn - NOAA Federal > <roy.mendelss...@noaa.gov> wrote: >> >> I am not expert in this, but I do notice that your .Rbuildignore is >> actually a link to a file of Kevin Ushey, and I don’t know that CRAN will >> deal with that correctly. Try instead to create a new .Rbuildignore with >> the same contents but is not pointer but a file. >> >> HTH, >> >> -Roy >> >> >>> On Jul 5, 2025, at 2:12 PM, Reed A. Cartwright <racartwri...@gmail.com> >>> wrote: >>> >>> Dear All, >>> >>> I submitted a new package ("ironseed") [1] to CRAN. I am not sure how >>> to address one feedback message or even what is causing it. It might >>> be related to Kevin Ushey's R scripts that I am using to configure the >>> package during installation [2]. The message that I received is below. >>> >>> """ >>> Please ensure that your functions do not write by default or in your >>> examples/vignettes/tests in the user's home filespace (including the >>> package directory and getwd()). This is not allowed by CRAN policies. >>> Please omit any default path in writing functions. In your >>> examples/vignettes/tests you can write to tempdir(). >>> -> tools/config.Rtools/config/configure.R >>> """ >>> >>> `tools/config.Rtools/config/configure.R` is not a file in my package. >>> So I assume that this report is saying that it is being created during >>> installation, but I can't reproduce it. My package does read and >>> execute `tools/config/configure.R` during installation, so right now >>> my guess is that my configure script is somehow creating >>> `tools/config.Rtools/config/configure.R` when I try to read >>> `tools/config/configure.R`. Any help figuring this out would be >>> appreciated. >>> >>> [1] https://github.com/reedacartwright/ironseed >>> [2] https://github.com/kevinushey/configure >>> >>> Thanks, >>> Reed >>> >>> -- >>> Reed A. Cartwright, PhD >>> Associate Professor of Life Sciences >>> TEACh Representative - Evolution and Computational Courses >>> School of Life Sciences and The Biodesign Institute >>> Arizona State University >>> ================== >>> Address: The Biodesign Institute, PO Box 876401, Tempe, AZ 85287-6401 USA >>> Packages: The Biodesign Institute, 1001 S. McAllister Ave, Tempe, AZ >>> 85287-6401 USA >>> Office: Biodesign B-220C, 1-480-965-9949 >>> Website: http://cartwrig.ht/ >>> >>> ______________________________________________ >>> R-package-devel@r-project.org mailing list >>> https://stat.ethz.ch/mailman/listinfo/r-package-devel >> ______________________________________________ R-package-devel@r-project.org mailing list https://stat.ethz.ch/mailman/listinfo/r-package-devel
