On Tue, Mar 4, 2025 at 8:16 AM Justin Forbes <jmforbes@xxxxxxxxxxx> wrote: > > On Sat, Feb 22, 2025 at 7:54 PM Benson Muite <benson_muite@xxxxxxxxxxxxx> wrote: > > > > > > Fedora has a policy to support only one kernel. Projects such as OpenHarmony support multiple kernels to enable reuse of components on devices with a wide range of compute capabilities - in particular mobile and edge devices. Is this something Fedora would consider doing? This would potentially benefit spins aimed for mobile and desktop use. > > So, the concept of flavors exists, and there is a possibility that we > could enable some additional flavors at some point. I know I have > been asked about rt kernels, 64K page size kernels for aarch64, etc. > The biggest problem we run into is the way that koji works. Each > arch is serialized, meaning if we add another flavor of aarch64, it > will double the build time for aarch64 kernels. Because Fedora is > completely open, I have no way to "stage" builds for things like > embargoed CVEs. This means that I can't commit the fix and start the > build until said CVE is public. As a result, each additional flavor > would have a significant impact on how quickly we can get critical CVE > fixes out to users. This is one of the main reasons that I am very > careful about additional flavors. I did float a proposal about > parallelizing builds which might make this less of an issue, though it > still wouldn't completely open flood gates. Fedora is only going to > support additional flavors officially if there are actual users and > testers to ensure that it is both worth the effort, and can maintain > some semblance of quality. > This isn't about flavors though, since flavors are all built from the same singular source package. This is about having separate source packages for different kernel trees that build installable and bootable kernels. -- 真実はいつも一つ！/ 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
