Reduce uv-build release frequency to lessen Gentoo maintenance burden
Problem
Gentoo must frequently rebuild uv-build, creating maintenance overhead and requiring custom patches for compatibility (e.g., 32‑bit support, LTO settings). They want a more stable release cadence or better integration to avoid repeated rebuilds.
Pain points
- Frequent uv-build releases force Gentoo to rebuild the package often, increasing maintenance burden
- Custom patches are required for 32‑bit support and LTO settings, adding complexity
Questions to verify
- Would Gentoo be willing to adopt a slower, predictable release cadence for uv-build if it reduced rebuild frequency?
- Would better built‑in compatibility (e.g., stable API) eliminate the need for Gentoo’s custom patches?
- Can clearer communication of uv-build’s intended usage (e.g., when to use uv_build vs uv) reduce confusion and unnecessary rebuilds?
Evidence
quote · @Anonymous
Why not set a policy of only updating once weekly, or even less frequently, with exceptions for important breaking changes or bug fixes?
quote · @Anonymous
Looks like it's being built with fat LTO by default (and gentoo patched to thin LTO). Which is fine if you want to spend CI cycles once to ship executables to thousands of users. If you compile from source and run the tool maybe once then they should consider going further and run with maybe opt-level=1, lto=off; halfway between release and debug.
Disclaimer: this card is distilled by AI from community discussions as “pain point evidence”. It is a starting point for need analysis and validation, not a “validated market need”. AI has analytical limits; please open the original discussion above to manually verify before key decisions.