From tom@@@k@||ber@ @end|ng |rom gm@||@com  Sun Oct 13 23:59:03 2024
From: tom@@@k@||ber@ @end|ng |rom gm@||@com (Tomas Kalibera)
Date: Sun, 13 Oct 2024 23:59:03 +0200
Subject: [Rd] R CMD check and CRAN's rust policy
In-Reply-To: <CAL3ufUKAEwf4BCePi710mK=hm7HJc+jj+XpqyegcZDegQNCfWA@mail.gmail.com>
References: <CAL3ufUKAEwf4BCePi710mK=hm7HJc+jj+XpqyegcZDegQNCfWA@mail.gmail.com>
Message-ID: <c5dde890-b3f0-48ca-ae93-63f6f5526eed@gmail.com>

On 10/13/24 19:30, Josiah Parry wrote:
> Hi all,
>
> I'm new to contributing to r-devel. The trunk of r-devel right now includes
> a `check_rust()` function for adherence to CRAN's evolving rust policy (see
> commit
> https://github.com/r-devel/r-svn/commit/6114d4126434c056b476cbc5db2657536c153d9a
> ).
>
> As it stands R 4.4.2 will codify CRAN policy on Rust as the R language's
> policy and will have deep implications for the language moving forward.  It
> would make *any* package that uses Rust to adhere to their policies.

R 4.4.2 will be released from the R-4-4-branch, not from the trunk. The 
change you have pointed to is only on the trunk, which would eventually 
become the next minor release, probably 4.5.0. Anything on the trunk is 
subject to change.

See https://svn.r-project.org/R/branches/R-4-4-branch/src vs 
https://svn.r-project.org/R/trunk

> I've submitted an issue as well as a patch at
> https://bugs.r-project.org/show_bug.cgi?id=18806.
>
> What is the process for submitting the bug and patch for review?

See https://www.r-project.org/bugs.html

But in short, submitting a PR to bugzilla about this as you have done is 
fine. Now it is the turn for R Core to consider if this should be a 
CRAN-only check or not.

Best
Tomas

>
> 	[[alternative HTML version deleted]]
>
> ______________________________________________
> R-devel at r-project.org mailing list
> https://stat.ethz.ch/mailman/listinfo/r-devel



[Rd] R CMD check and CRAN's rust policy
Tomas Kalibera