On 2025/07/04 10:36, Laurent Cheylus wrote:
> I read the replies from tb@ and Suart. Unfortunately, upstream project 
> uses frequently patched Rust crates: some permanently (rs-async, pubgrub, 
> tl), other only for some releases (now, patchs for reqwest-middleware).

It's in their control whether they decide to do it like that, or make
actual releases that OS packagers can use.

I looked at ruff and uv a few months ago and came to the conclusion that
between upstream's decision about that, resulting in a bunch of extra
work for updates, combined with the very frequent release cadence, that
they aren't really essential, and that pipx works for both, it probably
wasn't worth the contortions to get them into ports.

> I think it' better to download patched crates from GH and uses SUBST_CMD 
> to patch Cargo.toml as in my port.

SUBST_CMD is a bit of a pain for update-patches as you can only update
at the right point during build. tb's approach that doesn't include the
hash in the dir name, resulting in replacement Cargo.toml lines that
don't need to change dir name each time, does make this a little easier.

-+version-ranges = { path = "../pubgrub-${PUBGRUB}/version-ranges" }
++version-ranges = { path = "../pubgrub/version-ranges" }



> PS: I have also a port for the other main Astral-sh project, ruff (Python 
> linter in Rust) => ttps://github.com/jasperla/openbsd-wip/tree/master/
> devel/ruff
> 
> Laurent
>