Vitaly Zaitsev via devel kirjoitti 6.12.2021 klo 11.01:
On 06/12/2021 03:39, Bernie Innocenti via devel wrote:
What are the current Fedora packaging guideline regarding ABI
stability of shared libraries?
The package maintainer should ask upstream to bump the soversion field
and if it is rejected, bump it manually in downstream.
And here is the reference for this: Packaging Guidelines, section
"Downstream .so name Versioning" [1]. It is notable that the same
section also says this: "Under no circumstances should the unversioned
library be shipped in Fedora."
As for notifying about abi changes in packages, see the Updates policy
[2]. These items are relevant:
* When a proposed update contains an ABI or API change: notify a week in
advance both the devel list and maintainers directly (using the
packagename-maintainers@xxxxxxxxxxxxxxxxx alias) whose packages depend
on yours to rebuild or offer to do these rebuilds for them.
* Use a side-tag when dealing with mass builds of many packages, so they
can land at the same time. See Rawhide Gating/Multi Builds.
Otto
[1]:
https://docs.fedoraproject.org/en-US/packaging-guidelines/#_downstream_so_name_versioning
[2]: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/
_______________________________________________
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 on the list, report it: https://pagure.io/fedora-infrastructure
