> So how about splitting 'kernel-core' into a modules and
a kernel binary
> package? Like this:
>
> kernel-modules-core - the modules from current 'kernel-core'
> kernel-modules-standard - current 'kernel-modules' renamed (maybe
> skip rename, but I think it'll be less
> confusing that way).
> kernel-modules-{extra,internal} - no changes
>
> kernel-binary-bare - the kernel binary from current 'kernel-core'
> kernel-binary-uki-virt - unified kernel (same as 'kernel-unified-virt'
> in the test package repo).
> kernel-{doc,tools*,headers,...} - no changes
Yes, please! Such a split would be very welcome.
https://src.fedoraproject.org/fork/kraxel/rpms/kernel/commits/f37.newsplit
https://copr.fedorainfracloud.org/coprs/kraxel/kernel.testbuilds/
Did not (yet?) rename the kernel package to kernel-binary-bare. So the
kernel-modules -> kernel-modules-standard rename is there, and moving
the modules into kernel-modules-core. That opens up the question what
we should do with all the (non-module) files in /lib/modules/<version>/.
The modules.* files (generated by depmod) clearly belong into the
modules package.
The files copied over to /boot by the kernel-install grub plugin should
stay in the kernel binary package.
Not so sure about the other files (vdso for example). Leaving them in
kernel-modules-core should work fine as that package will continue to
be installed even when we replace the traditional kernel package with a
unified kernel package. But maybe it makes sense to move them into a
separate package?
My current split looks like this:
# rpm -ql kernel-core-6.0.9-300.newsplit.4.fc37.x86_64
/boot/.vmlinuz-6.0.9-300.newsplit.4.fc37.x86_64.hmac
/boot/System.map-6.0.9-300.newsplit.4.fc37.x86_64
/boot/config-6.0.9-300.newsplit.4.fc37.x86_64
/boot/initramfs-6.0.9-300.newsplit.4.fc37.x86_64.img
/boot/symvers-6.0.9-300.newsplit.4.fc37.x86_64.gz
/boot/vmlinuz-6.0.9-300.newsplit.4.fc37.x86_64
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/.vmlinuz.hmac
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/System.map
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/config
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/symvers.gz
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/vmlinuz
/usr/share/licenses/kernel-core
/usr/share/licenses/kernel-core/COPYING-6.0.9-300.newsplit.4.fc37
# rpm -ql kernel-modules-core-6.0.9-300.newsplit.4.fc37.x86_64 | grep -v /kernel/
/lib/modules
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/build
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/kernel
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/modules.block
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/modules.builtin
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/modules.builtin.modinfo
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/modules.drm
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/modules.modesetting
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/modules.networking
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/modules.order
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/source
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/systemtap
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/updates
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/vdso
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/vdso/vdso32.so
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/vdso/vdso64.so
/lib/modules/6.0.9-300.newsplit.4.fc37.x86_64/weak-updates
/usr/share/doc/kernel-keys/6.0.9-300.newsplit.4.fc37.x86_64
/usr/share/doc/kernel-keys/6.0.9-300.newsplit.4.fc37.x86_64/kernel-signing-ca-20140212.cer
/usr/share/doc/kernel-keys/6.0.9-300.newsplit.4.fc37.x86_64/kernel-signing-ca-20200609.cer
/usr/share/doc/kernel-keys/6.0.9-300.newsplit.4.fc37.x86_64/kernel-signing-ca.cer
comments?
take care,
Gerd