Dne 30. 06. 23 v 10:34 Benson Muite napsal(a):
There is at present no policy on when and why packages should be deprecated. Have made a proposal to allow deprecation of packages only when they fail to build
There is a catch. Packages which are FTBFS cannot be marked as deprecated, because there is no way to inject the `Provides: deprecated()` there without the build.
Vít
or are a security concern. In other cases, orphaning and retirement should be done. Comments and suggestions for improvement are welcome. This would also likely impact package review guidelines, since there are packages that people may want in Fedora, which build but do not have much upstream activity. 1) https://fedoraproject.org/wiki/Changes/DeprecationPolicy#Upgrade%2Fcompatibility_impact _______________________________________________ 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
Attachment:
OpenPGP_signature
Description: OpenPGP digital signature
_______________________________________________ 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
