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

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

2024-05-08 Thread Josiah Parry
polars be able to exist on CRAN. On Wed, May 8, 2024 at 4:06 PM Uwe Ligges wrote: > > > 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 i

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

2024-05-08 Thread Josiah Parry
l the work of creating a way to build, store, and retrieve the dependencies only for CRAN to decide they don't support it. On Wed, May 8, 2024 at 3:32 PM Ivan Krylov wrote: > В Wed, 8 May 2024 14:08:36 -0400 > Josiah Parry пишет: > > > With ChatGPT's ability to write autoconf, I

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

2024-05-08 Thread Josiah Parry
or has changed (and not give > a check warning nor error)." > > Neal > > [1]: https://cran.r-project.org/web/packages/policies.html > > > On Wed, May 8, 2024 at 11:03 AM Josiah Parry > wrote: > > > > I am sorry for blowing up this thread lately. > >

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

2024-05-08 Thread Josiah Parry
kage. Best, Yes, prqlr is a great Rust-based package! My other Rust based packages that are on CRAN are based, in part on prqlr. On Wed, May 8, 2024 at 11:51 AM Dirk Eddelbuettel wrote: > > On 8 May 2024 at 11:02, Josiah Parry wrote: > | CRAN has rejected this package with: >

[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

Re: [R-pkg-devel] Cannot repro failing CRAN autochecks

2024-05-08 Thread Josiah Parry
Thanks to @yutannihilation for pointing out that the issue repros on r-universe https://github.com/r-universe/r-arcgis/actions/runs/8990426306/job/24695887245 . Do folks know if there are any templates for the linux CRAN check? It appears that the r-lib/actions linux checks don't cover all of the

Re: [R-pkg-devel] Cannot repro failing CRAN autochecks

2024-05-07 Thread Josiah Parry
:40 Ivan Krylov wrote: > В 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 > <https://github.com/

[R-pkg-devel] Cannot repro failing CRAN autochecks

2024-05-07 Thread Josiah Parry
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

[R-pkg-devel] Linker / System Requirement

2024-05-07 Thread Josiah Parry
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

Re: [R-pkg-devel] Urgent Review of R Packages in Light of Recent RDS Exploit

2024-05-03 Thread Josiah Parry
I agree with Ivan here. And more generally, R is a fully featured programming language. You don't need just this one "exploit" (though, it really does feel like a feature to some degree lol!) to be a bad guy with R. You can link to a pre-compiled binary (like my team makes for an R package that

Re: [R-pkg-devel] puzzling removal of 'dotwhisker' from CRAN

2024-04-18 Thread Josiah Parry
Well, after trying to install the package, I believe the issue is because margins has been archived. https://cran.r-project.org/web/packages/margins/index.html You can check recursive dependencies using `tools::package_dependencies("pkg", recursive = TRUE)` which would help you in this case. I

Re: [R-pkg-devel] Suggesting an archived package in the DESCRIPTION file

2024-03-05 Thread Josiah Parry
My understanding is that the order of CRAN repos available in `options("repos")` are tried sequentially. So if cran.r-rproject.org is first, that will be tried. If the package is not available there, the next repository will be tried. I do appreciate the ease of release to R-universe quite a bit

Re: [R-pkg-devel] Changing package maintainers

2024-02-08 Thread Josiah Parry
name > and email address of the new maintainer. > > Best, > Josh > > > On Thu, Feb 8, 2024 at 10:38 AM Josiah Parry > wrote: > > > > I intend to change the maintainer of my package {sfdep} > > https://cran.r-project.org/package=sfdep. > > Is the process

Re: [R-pkg-devel] Changing package maintainers

2024-02-08 Thread Josiah Parry
[1] https://cran.r-project.org/web/packages/policies.html#Submission > > On February 8, 2024 8:37:50 AM PST, Josiah Parry > wrote: > >I intend to change the maintainer of my package {sfdep} > >https://cran.r-project.org/package=sfdep. > >Is the process as simple as submittin

[R-pkg-devel] Changing package maintainers

2024-02-08 Thread Josiah Parry
I intend to change the maintainer of my package {sfdep} https://cran.r-project.org/package=sfdep. Is the process as simple as submitting a new release where the DESCRIPTION file changes who has the role of `aut`? [[alternative HTML version deleted]]

Re: [R-pkg-devel] Native pipe in package examples

2024-01-25 Thread Josiah Parry
a.m., Henrik Bengtsson wrote: > > On Thu, Jan 25, 2024 at 7:48 AM Duncan Murdoch > wrote: > >> > >> On 25/01/2024 10:27 a.m., Josiah Parry wrote: > >>> Hey all, > >>> > >>> I've encountered use of the native pipe operator in the examp

[R-pkg-devel] Native pipe in package examples

2024-01-25 Thread Josiah Parry
Hey all, I've encountered use of the native pipe operator in the examples for 'httr2' e.g. request("http://example.com;) |> req_dry_run() Since r-oldrel (according to rversions::r_oldrel()) is now 4.2.3, can the native pipe be used in example code? I do notice that the package httr2 requires

Re: [R-pkg-devel] test failure: oldrel

2024-01-16 Thread Josiah Parry
Thanks for the update! Ill be submitting a change in the coming days and will report back :) On Tue, Jan 16, 2024 at 12:12 Dirk Eddelbuettel wrote: > > On 16 January 2024 at 10:28, Josiah Parry wrote: > | Oddly making the change has made CI happy. > | > https://github.com/R-Arc

Re: [R-pkg-devel] test failure: oldrel

2024-01-16 Thread Josiah Parry
Oddly making the change has made CI happy. https://github.com/R-ArcGIS/arcgisutils/actions/runs/7543315551/job/20534063601 It may be that the issue was OS related but I'm unsure since only oldrel for windows and macos check results are published

[R-pkg-devel] test failure: oldrel

2024-01-16 Thread Josiah Parry
Hey folks! I've received note that a package of mine is failing tests on oldrel. Check results: https://www.r-project.org/nosvn/R.check/r-oldrel-windows-x86_64/arcgisutils-00check.html I think I've narrowed it down to the way that I've written the test which uses `as.POSIXct(Sys.Date(), tz =

Re: [R-pkg-devel] Suggests with non-CRAN packages

2024-01-10 Thread Josiah Parry
AM Uwe Ligges wrote: > > > On 10.01.2024 15:35, Josiah Parry wrote: > > Thanks, all. As it goes, the package submission failed. The package that > > is suggested is available at https://r.esri.com/bin/ > > <https://r.esri.com/bin/> and as such provided `ht

Re: [R-pkg-devel] Suggests with non-CRAN packages

2024-01-10 Thread Josiah Parry
; Best, > Uwe Ligges > > > > > On 03.01.2024 18:19, Josiah Parry wrote: > > Thanks, both. I'm not familiar with Additional_repositories. Must the > > package source be specified there? Or can it be specified via > > documentation a la Rd file? > > > >

Re: [R-pkg-devel] Assigning an object to the global environment (shiny package)

2024-01-04 Thread Josiah Parry
Alternatively, you can create a new environment in your package and assign into it and fetch out of it. This is definitely safer and probably "more idiomatic." Hope that helps! # create a new environment

Re: [R-pkg-devel] [Rd] static html vignette

2024-01-04 Thread Josiah Parry
I understand that this doesn't actually *solve *your problem, but would like to offer an alternative perspective. I often find that vignettes may be most useful as an extended form of documentation. If you have a pkgdown site, you can use `usethis::use_article()` to create an article which will

Re: [R-pkg-devel] Suggests with non-CRAN packages

2024-01-03 Thread Josiah Parry
Thanks, both. I'm not familiar with Additional_repositories. Must the package source be specified there? Or can it be specified via documentation a la Rd file? On Wed, Jan 3, 2024 at 12:14 PM Uwe Ligges wrote: > > > On 03.01.2024 17:58, Duncan Murdoch wrote: > > On 03/01/2024 11:

Re: [R-pkg-devel] Suggests with non-CRAN packages

2024-01-03 Thread Josiah Parry
Lovely, thank you! On Wed, Jan 3, 2024 at 11:43 AM Uwe Ligges wrote: > > > On 03.01.2024 17:33, Josiah Parry wrote: > > I have a scenario where I have an exported function that requires the > > installation a package that *is not* available on CRAN. The body of the >

[R-pkg-devel] Suggests with non-CRAN packages

2024-01-03 Thread Josiah Parry
I have a scenario where I have an exported function that requires the installation a package that *is not* available on CRAN. The body of the function is generally: fx <- function() { rlang::check_installed("noncranpkg") noncranpkg::gx() } As required, this package is in the Suggests field.

Re: [R-pkg-devel] Update timing of machines on CRAN?

2023-12-04 Thread Josiah Parry
Unfortunately, it is often important for us to pay attention to what machines our code is being tested on. I think the point is more or less that we often find ourselves trying to make super small adjustments for machines and builds that are used by a number of users in the single digits. The

Re: [R-pkg-devel] Example files for functions reading binary files

2023-12-03 Thread Josiah Parry
Rafael, I believe the issue is that packages cannot include binary *executables.* If you have a binary file (such as a parquet file) in inst/extdata, I do not think that would be a problem. It would be a good idea to ensure that that file is small, though. I think downloading a file is a big no

Re: [R-pkg-devel] NOTE: Examples with CPU time > 2.5 times elapsed time

2023-12-03 Thread Josiah Parry
In these cases, I unfortunately find the best approach to be to wrap the examples in `if (interactive()) ` to ensure that they will not be ran on CRAN tests machines. It hampers the checks of CRAN but it makes it possible to get usable code to users. On Sun, Dec 3, 2023 at 9:54 AM Artur Araujo