> somewhere between 1/6 and 1/3 of packages are lagging, in Rawhide.
If you are concerned about shipping old packages, then upstream-release branching is the *solution*, not the problem.
this. and the situation's more severe if you're on current release F44 ... but mine's the perspective of a user org that needs packaging/releases that Fedora distro doesn't -- or won't -- provide. for me too, what Fedora provides often lags in release version, or has build config limitation, or ... COPR was a solution for some time, but as needs evolved the capabilities i needed often weren't of interest. it became limiting. where i've ended up is with a very stable Fedora distro 'core'. its maintenance and upgrade cadence fit well. and ALL server apps, and many DESKTOP apps are locally rpm built, distributed and maintained; each built in a curated venv/tree, with specific (often) upstream-specified dependency trees and my choice of toolchains; and, installs are isolated in /some/path/SERVER_APP tree. that means all I need -- or more accurately, benefit from -- is modern/up-to-date `mock`. automation is straightforward. when that stops fitting, i've LFS and a DIY build system. not fun to maintain, but works ... i'm absolutely clear that little if any of 'my' build specs would come anywhere close to meeting distro guidelines. but the tools to do THAT^ -- in my specific case, mock -- are invaluable. and for now set Fedora apart. -- _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new
