On Sat, Nov 12, 2022 at 12:49 AM Simon Urbanek
wrote:
>
> this does not directly address your question, but I think it would make a lot
> of sense to standardize the process, given how many issues there were with
> packages using Rust (mainly not detecting compilers correctly, not supplying
> s
On 12 November 2022 at 19:27, Jeroen Ooms wrote:
| On Sat, Nov 12, 2022 at 12:49 AM Simon Urbanek
| wrote:
| >
| > this does not directly address your question, but I think it would make a
lot of sense to standardize the process, given how many issues there were with
packages using Rust (mainl
Jeroen,
sorry, I think you misunderstood: CRAN machines have the compilers, but the
packages were not detecting it properly and/or were violating the CRAN policies
as noted, so that's why I was saying that it would make sense to have a unified
approach so that each package author doesn't have t
On 13 November 2022 at 08:15, Simon Urbanek wrote:
| sorry, I think you misunderstood: CRAN machines have the compilers, but the
packages were not detecting it properly and/or were violating the CRAN policies
as noted, so that's why I was saying that it would make sense to have a unified
appro
No, because I don't use Rust. That's why I was saying that the Rust users
should get together and create a such package. Some of the packages listed have
experience in fixing the problems, so I would hope they can provide guidance or
a good starting point. This is something for the interested co
