On Thu, Jan 4, 2024 at 7:50 AM Sam Varshavchik <mrsam@xxxxxxxxxxxxxxx> wrote: > > Oron Peled writes: > > > • I.e: a developer that need cross-compilation, install the wanted > > toolchain(s) and all library packages are immediately available from standard > > repositories. > > > > I guess Fedora people that work on ARM/ARM64/RISC-V would love such a > > support. > > There are a number deb packaging policies that rpm would be wise to adopt. > > A package's shared libraries get rolled into a separate <library><soname> > package right off the bat. An ABI break and a transition where both the new > and the old libraries must coexist becomes a nothing-burger. The updated > package's libraries go into a subpackage with, effectively, a new name that > does not cause the older library's uninstallation. There is no need to > create a compat package. It's the same package, from the previous version. > That is not a deb vs rpm thing, plenty of rpm distributions do it. We don't do it in Fedora because we don't want it to be automatic for older libraries to hang around, plain and simple. -- 真実はいつも一つ！/ Always, there's only one truth! -- _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx 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/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
