Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-09 Thread Josiah Parry
> > ...but that's a luxury someone would have to pay for. > I'd happily give up my Netflix subscription for this. I suspect the R-foundation/consortium could assist as well? Referring to the "Using Rust in CRAN packages" document we must be able to ...download a specific version from a secure an

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-09 Thread Dirk Eddelbuettel
Software Heritage (see [1] for their website and [2] for a brief intro I gave at useR! 2019 in Toulouse) covers GitHub and CRAN [3]. It is by now 'in collaboration with UNESCO', supported by a long and posh list of sponsors [4] and about as good as it gets to 'ensure longevity of artifacts'. It

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-09 Thread Ivan Krylov via R-package-devel
В Wed, 8 May 2024 16:01:23 -0400 Josiah Parry пишет: >- I'll see if I can get the configure.ac to make the appropriate > Rscript call for configure.win. > - I think the idea of having a single `confgure.ac` file to > generate both configure and configure.win is nice. Guidance with > Git

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Vladimir Dergachev
On Wed, 8 May 2024, Josiah Parry wrote: Yes, prqlr is a great Rust-based package! My other Rust based packages that are on CRAN are based, in part on prqlr. If there are many packages based on Rust that require common code, would it make sense to make a single "rust" compatibility pack

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Ben Bolker
Zenodo and OSF (see e.g. ) are both non-profit organizations that support archiving -- that is, they both make stronger guarantees of permanent availability than GitHub does. Possibly Software Heritage https://www.softwareheritage.org/features/ ?

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Josiah Parry
That's a good point! My apologies for not making that abundantly clear. Regardless, I think it is a fair ask to not submit massive tarballs of dependencies. Clarifying how we might be able to store the dependencies *outside *of CRAN would be good to figure out. This would help packages like polars

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Uwe Ligges
On 08.05.2024 17:56, Josiah Parry wrote: Thank you, Dirk. This was a direct email from a CRAN member and not part of the automatic checks. The whole email is below. I think the intent of the message is "please resubmit." Well, the CRAN maintainer has not spotted this is abour rust code. This

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Josiah Parry
Thank you, Ivan, for your really thoughtful feedback! I really appreciate it! - I'll see if there are any base R packages that support SHA-2 or SHA-3. - I'll see if I can get the configure.ac to make the appropriate Rscript call for configure.win. - I think the idea of having a sing

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Ivan Krylov via R-package-devel
В Wed, 8 May 2024 14:08:36 -0400 Josiah Parry пишет: > With ChatGPT's ability to write autoconf, I *think *I have something > that can work. You don't have to write autoconf if your configure.ac is mostly a plain shell script. You can write the configure script itself. Set the PATH and then exec

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Josiah Parry
Thank you, Neal! I took some inspiration from the arrow-r github repo and ch 1.2 of the manual *If your configure script needs auxiliary files, it is recommended that you > ship them in a tools directory (as R itself does).* With ChatGPT's ability to write autoconf, I *think *I have something t

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Josiah Parry
Thank you, Dirk. This was a direct email from a CRAN member and not part of the automatic checks. The whole email is below. I think the intent of the message is "please resubmit." Thanks, we see: >Size of tarball: 18099770 bytes Please reudce to less than 5 MB for a CRAN package. Best,

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Dirk Eddelbuettel
On 8 May 2024 at 11:02, Josiah Parry wrote: | CRAN has rejected this package with: | | * Size of tarball: 18099770 bytes* | | *Please reudce to less than 5 MB for a CRAN package.* Are you by chance confusing a NOTE (issued, but can be overruled) with a WARNING (more severe, likely a must-be-

Re: [R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Neal Richardson
CRAN policy [1] says: "If the sources are too large, it is acceptable to download them as part of installation, but do ensure that the download is of a fixed version rather than the latest." So you could try downloading the source in your configure script. Though be careful not to be bitten by this

[R-pkg-devel] Overcoming CRAN's 5mb vendoring requirement

2024-05-08 Thread Josiah Parry
I am sorry for blowing up this thread lately. I've submitted a package to CRAN that uses Rust which thus requires dependencies to be vendored. https://github.com/R-ArcGIS/arcgisutils/ The vendored dependencies are 18mb when zipped and 16.4mb when zipped with XZ -9e. The *installed package size is