From: Theo Buehler Subject: Re: Porting astral-sh/uv To: Laurent Cheylus , ports@openbsd.org Date: Fri, 4 Jul 2025 14:36:05 +0200 On Fri, Jul 04, 2025 at 01:01:38PM +0100, Stuart Henderson wrote: > 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. Yes. > 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. Yes, it's not going to be pretty. As someone who usually only needs to deal with the python ecosystem when there's already enough other pain involved and thus has absolutely no patience for its idiosyncrasies, I'd very much appreciate an up-to-date port over having to remember how to fiddle with pip* and venvs. (I needed to look at some trailofbits stuff that relied heavily on ruff and uv, and it took ages before I could get started). So the attached port does some polishing like fixing missing deps and wantlib and installing the shell completions. It should be pretty much equivalent to Laurent's port in openbsd-wip except that I didn't pull in the retry counting patches since it wasn't clear that that was about. There's also the question if it should go into devel or sysutils. I have no real opinion on that. Someone needs to review this properly before it can go in. Once that's done and if Laurent or Denis are willing to take maintainer and want to keep this reasonably up-to-date, I think I'll be ok with someone else importing it.