Re: Help remove scriptlets from the kernel?
> "JLT" == Jason L Tibbitts writes: JLT> One fun thing is that I have no idea how file triggers interact JLT> with packages which are installed multiple times. I now know: it works the way I hope it does, so the scriptlets I suggested for auto-running depmod should work properly. As a bonus, I think it would slightly simplify third party kernel module packages. - J< ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: toolchain requirements for external kernel modules
On 2/19/19 10:47 AM, Dulaney wrote: On Gearr 18, 2019 aig 12:26:04f -0800, sgrìobh Laura Abbott: Yes, that was the case I was concerned about with gcc being updated. I guess the case would be where the kernel gets built with a different gcc that isn't yet on a local system. Doing a batched bodhi update could fix this for stable releases but we don't have that on rawhide. Requiring the sync also seems like a pain to deal with. Laura So, just out of curiosity, why can't these be in their own rpm(s) that get updated every time gcc does? If I'm reading you correctly, the gcc modules are dependent on gcc, not the kernel features on specific versions of the gcc modules. No, these plugins are tied to the kernel itself and can be updated with each kernel version. They need to exist in the kernel spec file at kernel build time. They aren't dependent on the gcc version per se but they need to get rebuilt each time there is a new gcc. Thanks, Laura ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
Re: toolchain requirements for external kernel modules
On Gearr 18, 2019 aig 12:26:04f -0800, sgrìobh Laura Abbott: > Yes, that was the case I was concerned about with gcc being updated. > I guess the case would be where the kernel gets built with a different > gcc that isn't yet on a local system. Doing a batched bodhi update > could fix this for stable releases but we don't have that on rawhide. > Requiring the sync also seems like a pain to deal with. > > Laura So, just out of curiosity, why can't these be in their own rpm(s) that get updated every time gcc does? If I'm reading you correctly, the gcc modules are dependent on gcc, not the kernel features on specific versions of the gcc modules. -- Tapadh leabh, Dulaney. ___ kernel mailing list -- kernel@lists.fedoraproject.org To unsubscribe send an email to kernel-le...@lists.fedoraproject.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/kernel@lists.fedoraproject.org
