Re: combined dependencies?
* Michael Tautschnig [2011-08-24 14:31 +0200]:
> > Its not any header package: dkms needs the _appropriate_ header
> > package matching the installed kernel package. If
> > linux-image-2.6.39-1-amd64 is installed, then dkms needs
> > linux-headers-2.6.39-1-amd64. If linux-image-3.0-1-amd64 is
> > installed in parallel, then dkms needs linux-headers-3.0-1-amd64,
> > too.
> > Its just an example, anyway.
> Isn't all you want (with l-i-1 = linux-image-2.6.39-1-amd64, l-h-2 =
> linux-headers-3.0-1-amd64, etc.)
> Depends: (l-i-1, l-h-1) | (l-i-2, l-h-2) | ...
The above depends line does not ensure that "the _appropriate_ header
package" is installed since an old image and an old header would satisfy
Given that I have linux-image-3.14 and linux-image-3.20 installed, but
not dkms nor any header package, installing dkms would force me to
install in one of the above cases _any_ header package matching an
installed kernel and in the other one to install _all_ header packages
matching an installed kernel.
If linux-headers-3.14 wouldn't be available in Debian anymore, the
originally proposed combined dependencies would force me to remove
linux-image-3.14 if I install dkms. Do we really want to force users to
remove old kernel images (which they would possibly like to keep as
fallback) if they install dkms the first time?
What you proposed does not lead to forced removals of old kernel images,
but, as already mentioned, it does not ensure the appropriate header