Add r-h3jsr

[matthewfeickert]

Required for PR #32249

• Add h3jsr v1.3.1.
  • c.f. https://github.com/obrl-soil/h3jsr
• Note to reviewers, I have intentionally not added myself to this recipe as a maintainer. @obrl-soil (cc @lauren-obrien) is being asked (with no advanced notice) and I will assist with any questions that they might have.

This recipe was generated by

$ pixi init conda-forge-cran-generate && cd conda-forge-cran-generate && pixi add git conda 'conda-build 3.27.0' python && pixi run git clone https://github.com/bgruening/conda_r_skeleton_helper.git && cd conda_r_skeleton_helper
$ echo "r-h3jsr" > packages.txt
$ echo "    - obrl-soil" >> extra.yaml
$ pixi run python run.py

and then manually edited for cosmetics and package metadata.

DESCRIPTION file:

Package: h3jsr
Type: Package
Title: Access Uber's H3 Library
Version: 1.3.1
Date: 2023-01-21
Authors@R: person("Lauren", "O'Brien", email = "obrlsoilau@gmail.com", role = c('aut', 'cre'), comment = c(ORCID = "0000-0002-7336-2171"))
Description: Provides access to Uber's H3 library for geospatial indexing via its JavaScript transpile 'h3-js' <https://github.com/uber/h3-js> and 'V8' <https://github.com/jeroen/v8>.
License: Apache License (>= 2)
Encoding: UTF-8
LazyData: true
Depends:
    R (>= 2.10)
SystemRequirements:
    V8 engine version 6+ is needed for modern JS and WASM support. On Debian / Ubuntu install either libv8-dev or libnode-dev, on Fedora use v8-devel.
Imports:
    geojsonsf,
    methods,
    sf,
    tidyr,
    utils,
    V8 (>= 4.0.0)
Suggests:
    covr,
    dplyr,
    ggplot2,
    knitr,
    rmarkdown,
    testthat
RoxygenNote: 7.2.3
VignetteBuilder: knitr
URL: https://obrl-soil.github.io/h3jsr/
BugReports: https://github.com/obrl-soil/h3jsr/issues

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Package does not ship static libraries. If static libraries are needed, follow CFEP-18.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/r-h3jsr/meta.yaml) and found it was in an excellent condition.

[matthewfeickert]

👋 @obrl-soil would you be willing to be a maintainer for your R package on conda-forge? There's no commitment to work on this, and the only "work" would be approving a PR if the conda-forge/r conda-forge team doesn't do it first when there is a new release (and it seems that there probably won't be many).

The CI linter needs a response of some form from everyone listed under recipe-maintainers.

[matthewfeickert]

Apache-2.0 does not exist under {{ environ["PREFIX"] }}/lib/R/share/licenses/ and so needs to be manually added from https://github.com/obrl-soil/h3jsr/blob/ac2c2fdcf1ed584e864f56273f4e4145865b5c5e/LICENSE.md.

[github-actions]

Hi! This is the staged-recipes linter and I found some lint.

File-specific lints and/or hints:

• recipes/r-h3jsr/meta.yaml:
  • lints:
    • The following maintainers have not yet confirmed that they are willing to be listed here: obrl-soil. Please ask them to comment on this PR if they are.

[obrl-soil]

Hi, no problems from my end.

[github-actions]

Hi! This is the staged-recipes linter and your PR looks excellent! 🚀

[matthewfeickert]

Thanks @obrl-soil!

[matthewfeickert]

@conda-forge/help-r, ready for review!

[matthewfeickert]

Tagging @conda-forge/staged-recipes as well to hopefully get this merged this week.

[github-actions]

To help direct your pull request to the best reviewers, please mention a topic-specifc team if your recipe matches any of the following: conda-forge/help-c-cpp, conda-forge/help-cdts, conda-forge/help-go, conda-forge/help-java, conda-forge/help-julia, conda-forge/help-nodejs, conda-forge/help-perl, conda-forge/help-python, conda-forge/help-python-c, conda-forge/help-r, conda-forge/help-ruby,or conda-forge/help-rust. Thanks!