Florian,
this does not directly address your question, but I think it would make a lot
of sense to standardize the process, given how many issues there were with
packages using Rust (mainly not detecting compilers correctly, not supplying
source code, unsolicited writing into user's
On 11 November 2022 at 16:06, Ivan Krylov wrote:
| В Fri, 11 Nov 2022 12:54:52 +
| "Grose, Daniel" пишет:
|
| > * checking sizes of PDF files under 'inst/doc' ... WARNING
| > 'gs+qpdf' made some significant size reductions:
| > compacted 'cpop.pdf' from 805Kb to 547Kb
| > consider
Hi Matthias,
Thank you very much for your response!
Putting the entire compiler toolchain of Rust into an R package is likely
just too much (it would need to compile the entire LLVM compiler which
would take hours just to build alone).
However, it is a very interesting idea to consider with
Hi Florian, I am doing something similar with Swi-Prolog. Feel free to contact
me if needed. My steps were:Get swipl to compile on Windows, MSYS2, then
Rtools4.2.Then, an R package rswipl that just includes the swipl runtime for
those people who don't have swipl installed. Then (basically
В Fri, 11 Nov 2022 12:54:52 +
"Grose, Daniel" пишет:
> * checking sizes of PDF files under 'inst/doc' ... WARNING
> 'gs+qpdf' made some significant size reductions:
> compacted 'cpop.pdf' from 805Kb to 547Kb
> consider running tools::compactPDF(gs_quality = "ebook") on these
> files
Hi
I have the file cpop.ltx file (containg LaTeX) in my package which gets
processed to produce a pdf file for the vignettes when the package gets
installed. However, CRAN checks give
* checking sizes of PDF files under 'inst/doc' ... WARNING
'gs+qpdf' made some significant size reductions:
Hi all,
Are there any current recommendations on integrating Rust (and Cargo, its
official package manager) in an R package complying to CRAN's policies?
To be clear: This question is not about how to integrate Rust in the
package, it is about how to do it without creating friction with the CRAN
