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.

Attachment: pgphaQFO76cNT.pgp
Description: PGP signature

--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam, report it: 
https://pagure.io/fedora-infrastructure/new_issue

Reply via email to