Thanks, Ivan!
As you can see, the directory is ignored already
https://github.com/R-ArcGIS/arcgisutils/blob/ff8a0a1b936e27be16ac866aa16605b973d435c7/.Rbuildignore#L14
The directory is created in the Makevars after the zip is untarred:
https://github.com/R-ArcGIS/arcgisutils/blob/ff8a0a1b936e27be
В Tue, 7 May 2024 21:40:31 +0300
Ivan Krylov via R-package-devel пишет:
> It's too late for Makevars to exclude files from the source package
> tarball. Use .Rbuildignore instead:
Sorry, that was mostly misguided. .Rbuildignore won't help with the
contents of the Rust vendor tarball.
1. Can you
В Tue, 7 May 2024 14:03:42 -0400
Josiah Parry пишет:
> This NOTE does not appear in Ubuntu, Mac, or Windows checks
> https://github.com/R-ArcGIS/arcgisutils/actions/runs/8989812276/job/24693685840
That's a bit strange. It fires for me in a local R CMD check for a test
package even without --as-c
Hi Josiah,
Indeed, the right thing to do is to declare the library in the
SystemRequirements file. However, other than some specific documented
usages which affect how R builds the package (e.g. C++ standards and
GNU make), I believe the field is meant more just to inform users of
the external dep
I've submitted an R package to CRAN and am failing checks *only on Debian*
https://win-builder.r-project.org/incoming_pretest/arcgisutils_0.3.0_20240507_194020/Debian/00check.log
This NOTE does not appear in Ubuntu, Mac, or Windows checks
https://github.com/R-ArcGIS/arcgisutils/actions/runs/8989
In my Makevars file (linked below) I link to ssl by adding `-lssl` to
`PKG_LIBS`. Since I do this, does libssl need to be added to the System
Requirements field?
Makevars:
https://github.com/R-ArcGIS/arcgisgeocode/blob/8194a478a616f7ddc3a25bcb024c0534007bcd51/src/Makevars#L4
If so, is there a pla
