RE: cargo fetch

[Marcin Gondek <drixter%e-utp.net@localhost>]

Hi All,

Just looked on their discussion forum.

"I would also recommend that you download the files directly from the CDN instead of going through our API servers: e.g. https://static.crates.io/crates/libc/0.2.185/download or https://static.crates.io/crates/libc/libc-0.2.185.crate. That addresses the rate limit concern mentioned in xxxx  (comment) since the 1 req/sec limit only applies to our API servers."

was
https://crates.io/api/v1/crates/serde/1.0.0/download 
could be
https://static.crates.io/crates/serde/serde-1.0.0.crate
or
https://static.crates.io/crates/serde/1.0.0/download

I've still no responses from them, not sure that we need to wait, maybe we should follow with static and no-api approach and we are good.

Thanks,

--
Marcin Gondek / Drixter
http://fido.e-utp.net/
AS56662

-----Original Message-----
From: Jonathan Perkin <jperkin%pkgsrc.org@localhost> 
Sent: Monday, June 1, 2026 2:37 PM
To: Adam <adam%netbsd.org@localhost>
Cc: Marcin Gondek <drixter%e-utp.net@localhost>; NetBSD tech-pkg <tech-pkg%pkgsrc.org@localhost>
Subject: Re: cargo fetch

* On 2026-06-01 at 13:27 BST, Adam wrote:

>My patch, which can be applied when Marcin gets the answer from crates.io:

I was just writing something similar ;)  This works for me with a couple of test packages, including ones with "+" distfiles like devel/cargo-c.

-- 
Jonathan Perkin                    pkgsrc.smartos.org
Open Source Complete Cloud   www.tritondatacenter.com