Packages are supposed to work when mounted in a read-only filesystem... using
writeLines seems like a very bad idea since you can't assume the package
install is writeable when it is run, and running code from tmp is a security
hole.
If you absolutely cannot think of a way around running code from generated
files, then maybe you should use textConnection to run from internal RAM.
On February 4, 2025 1:11:10 PM PST, Josiah Parry <josiah.pa...@gmail.com> wrote:
>I'm running R CMD check for my package {calcite} (source:
>https://github.com/r-arcGIS/calcite) which is failing due to what *looks* like
>a bug.
>
>R CMD check fails at "checking for future file timestamps"
>
>I get this error: ...Error in if (abs(unclass(now_local) -
>unclass(now)[1]) > 300) missing value where TRUE/FALSE needed.
>
>It seems that an NA is being generated somehow during this check but I'm
>unsure how.
>
>One thing that comes to mind is that the file that contains all of my
>function definitions is generated using writeLines() but the output of `
>file.info()` looks normal to me.
>
>Have others encountered this? I'm on R 4.4.0 Puppy Cup
>
>platform aarch64-apple-darwin20
>arch aarch64
>os darwin20
>system aarch64, darwin20
>status
>major 4
>minor 4.0
>year 2024
>month 04
>day 24
>svn rev 86474
>language R
>version.string R version 4.4.0 (2024-04-24)
>nickname Puppy Cup
>
> [[alternative HTML version deleted]]
>
>______________________________________________
>R-package-devel@r-project.org mailing list
>https://stat.ethz.ch/mailman/listinfo/r-package-devel
--
Sent from my phone. Please excuse my brevity.
______________________________________________
R-package-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-package-devel
