> It's kind of gross, but if you need a local solution, you could put
your own executable `cp` script on your PATH somewhere, and have that
do something "smart" when it's invoked by R.
Hah! Currently I opted out to using pkgbuild functions and specified
`Config/build/copy-method: link` in my DESCR
> I think the reason is simplicity. The build process can add, delete or
modify files. You wouldn't want that to happen on the original source
files, so R copies the files to a temporary location to run things.
> If it applied .Rbuildignore first, then important files for the build
might not be
Hi Alexey,
It's kind of gross, but if you need a local solution, you could put
your own executable `cp` script on your PATH somewhere, and have that
do something "smart" when it's invoked by R. One way to detect that
would be to check if the `R_CMD` environment variable is set. For
example:
https
On 2024-08-28 5:59 p.m., Alexey Sergushichev wrote:
Hi,
Is there any reason why .Rbuildignore is not used before copying package
files in R CMD build?
For some of the packages I develop I have rather large directories with
miscellaneous files for testing and other purposes. They are in my
.Rbui
Hi,
Is there any reason why .Rbuildignore is not used before copying package
files in R CMD build?
For some of the packages I develop I have rather large directories with
miscellaneous files for testing and other purposes. They are in my
.Rbuildignore (and .gitignore) file, but that doesn't preve
