On Fri, Jun 12, 2015 at 08:06:04AM -0400, Josh Boyer wrote: > > Well, and linux-firmware, which isn't needed at runtime but is pulled > > in for kernel upgrades, and which to my knowledge is not needed in any > > cloud environments. You might be the right person to talk to about > > figuring out if we can do anything about this. > A post install scriptlet that removes the files in the cloud > kickstarts is about as far as I'm going to go. I'm not dropping the > Requires from the kernel-core package and leave everyone else in the > lurch. Another option would be a dummy package that Provides > linux-firmware, but that also runs the risk of non-cloud instances > getting it installed since we don't have separate repos. It's unfortunate that the dependencies can't be expressed in a richer way here. It's not that the kernel requires that package... the hardware does. Even if we remove it in the cloud kickstarts, it gets pulled back in on update, because it's a "Requires(pre)". Even if the package left that out, and we relied on something else to make sure it's in place on real hardware (e.g. anaconda pulls it in, or even just have it a base group in comps), I'm not sure how to tell RPM to order it properly during initial install otherwise. (Short of special-casing in anaconda, which, ugh.) > (The third "option" is a separate cloud kernel package but that would > make the rework we did in f22 pointless and wasted and we've already > had that discussion.) Hmmmm -- what about making linux-firmware a Requires(Pre) for kernel-modules instead of kernel-core? -- Matthew Miller <mattdm@xxxxxxxxxxxxxxxxx> Fedora Project Leader _______________________________________________ cloud mailing list cloud@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/cloud Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
