🛠️Gentoo Package Manager Struggles with uv-build Dependency
Gentoo users face endless uv-build rebuilds
TL;DR
Gentoo users face issues with uv-build, a Rust-based backend, leading to frequent rebuilds and longer build times. The uv-build dependency causes packages to lose keywords, impacting Gentoo users and developers.
Gentoo users are facing issues with the uv-build dependency, a Rust-based backend, causing packages to lose keywords and requiring frequent rebuilds. This dependency is causing significant delays and inefficiencies, particularly for users of source distributions. The uv-build backend, while large and complex, offers minimal benefits over simpler alternatives like flit-core, which is only 45 KiB in size. Gentoo users will spend hours building new uv-build versions repeatedly, impacting their workflows and productivity.
Key Points
Gentoo users need to build uv-build from source, a time-consuming process.
uv-build backend is large and written in Rust, with wheels between 1.2 MiB and 1.5 MiB.
Flit-core, a pure Python backend, is only 45 KiB in size, offering a lighter alternative.
The uv-build backend is used by project developers, contributors, CI/CD workflows, and users of source distributions.
The Gentoo uv ebuild already has two hacks to build uv on 32-bit platforms.
Why It Matters
Gentoo users and developers are impacted by the uv-build dependency, facing frequent rebuilds and longer build times. The uv-build backend, while large and complex, offers minimal benefits over simpler alternatives like flit-core. Gentoo users will spend hours building new uv-build versions repeatedly, impacting their workflows and productivity.
Comments
Be the first to comment
Enjoyed this article?
Get it daily. 7am. Free. Reads in 5 minutes.
Join 3,568 builders reading daily.