>> >> I recently noticed that kernel packages are now split into three
>> >> subpackages (linux-base-VERSION, linux-binary-VERSION,
>> >> linux-modules-VERSION).
>> >>
>> >> Does anyone know why this is?  I'm trying to imagine scenarios where
>> >> that could be an advantage, but I'm coming up short.
>> >
>> >>From the changelog
>> >
>> > [ Bastian Blank ]
>> >   * Introduce a base package for udebs as well:
>> >     - Introduct linux-base.
>> >     - Rename kernel-image to linux-binary.
>> `aptitude` doesn't seem to find any "kernel-image" packages.
> Presumably because it's the name of a virtual package.

If you look at https://packages.debian.org/trixie/kernel-image you'll
see that while `kernel-image` is a virtual package, there are real
packages whose name starts with "kernel-image",
so `aptitude search kernel-image` should have found them, tho apparently
the fact that they're "DI only" makes them not show up somehow.

>> And also IIUC the main benefit of the split is to merge the
>> `linux-binary` part of the old `linux-image` with the old
>> `kernel-image`?
> If you look at the page I referenced earlier, you can rightclick on
> its companion package's name and get to:
>
>   https://packages.debian.org/forky/linux-base-6.19.8+deb14-amd64
>
> in another tab. Then click on "list of files" on each of those pages
> and look at the lists.

I don't need that: I had already done `dpkg -L` on those new packages to
see their content.  But their contents only tell me "the sum is the same
as the previous big package" but doesn't say why the big package
was split.


=== Stefan


Reply via email to