From Fedora Project Wiki
(Document Bugzilla trackers) |
(Cross-Distribution Collaboration) |
||
| Line 2: | Line 2: | ||
This page collects some technical details related to [[Changes/PortingToModernC]]. | This page collects some technical details related to [[Changes/PortingToModernC]]. | ||
== Cross-Distribution Collaboration == | |||
A mailing list has been set up to exchange issues and observations of wider interest: [https://subspace.kernel.org/lists.linux.dev.html c-std-porting@lists.linux.dev] ([https://lore.kernel.org/c-std-porting/ archive]) | |||
Further resources will follow as needed. | |||
== Fedora Bug Tracking == | == Fedora Bug Tracking == | ||
Revision as of 12:05, 2 November 2022
Porting Fedora to Modern C
This page collects some technical details related to Changes/PortingToModernC.
Cross-Distribution Collaboration
A mailing list has been set up to exchange issues and observations of wider interest: c-std-porting@lists.linux.dev (archive)
Further resources will follow as needed.
Fedora Bug Tracking
Not every build issue will have a bug in Bugzilla. But if there is no upstream with a mailing list or issue tracker to submit fixes to, it makes sense to create a bug in Bugzilla, especially for cross-distribution collaboration.
Currently, these trackers exist:
- PortingToModernC Umbrella tracker for the tracker bugs below.
- PortingToModernCExemptions Bugs which document that certain packages could not be switched to C99 or later language standards. Typically these packages keep building with
-std=gnu89. - PortingToModernCHelpNeeded Bugs where help from the package maintainer is needed to address the issue(s).