[R-pkg-devel] NOTEs in packages using Rust

savvy is opposed to supporting CRAN publication

Hi Naras, then I can't help you there! Last I checked, savvy is opposed to
supporting CRAN publication

On Thu, Jun 20, 2024 at 12:19?PM Balasubramanian Narasimhan <
naras at stanford.edu> wrote:

I?m using savvy but the version on CRAN uses extendr.

Could you clarify?

I?m not sure I know at which point to intervene in Makevars to fix things
myself?

Thanks.
-Naras

Balasubramanian Narasimhan
------------------------------
*From:* Josiah Parry <josiah.parry at gmail.com>
*Sent:* Thursday, June 20, 2024 9:08:10 AM
*To:* Balasubramanian Narasimhan <naras at stanford.edu>
*Cc:* r-package-devel at r-project.org <r-package-devel at r-project.org>
*Subject:* Re: [R-pkg-devel] NOTEs in packages using Rust

Hi Naras, this should be handled by the Makevars itself. Are you using
extendr to do this?

Using `rextendr::use_cran_defaults()` should handle it for you. Then you
can use `rextendr::vendor_pkgs()` to handle vendoring.


On Thu, Jun 20, 2024 at 11:57?AM Balasubramanian Narasimhan <
naras at stanford.edu> wrote:

I am preparing an update of Clarabel to synchronize with the upstream
repo. When checking the package, I get NOTEs such as:

    Found the following CITATION file in a non-standard place:
       src/rust/vendor/clarabel/CITATION.bib
    Most likely ?inst/CITATION? should be used instead.

    Found the following sources/headers not terminated with a newline:

 src/rust/vendor/lapack-sys/lapack/LAPACKE/src/lapacke_cgetsqrhrt_work.c

etc.

These are coming from the vendored sources and I plan to note that in my
submission. Will that suffice?

I will, of course, let the crate authors know and even submit a PR, but
not sure if it will yield an update in a reasonable time.

PS. Excluding files in tarring or fixing newlines are not an option as
the checksums will fail.

Thanks.

-Naras


        [[alternative HTML version deleted]]

        [[alternative HTML version deleted]]