Strict kernel module dependencies (was: RPM dependency rationale (and kernel packages)?)
Jeff Johnson
jbj at redhat.com
Wed Aug 20 18:03:34 UTC 2003
On Wed, Aug 20, 2003 at 11:55:51AM +0300, Axel Thimm wrote:
>
(snipped, but basically we agree, except "flavor" is different than "arch"
because there are different set values involved).
> > There's no easy answer, but more than adding arch to a kernel Provide:
> > is needed.
>
> If Red Hat doesn't change the current (arch, flavour) policy (and
> there is no reason to) the suggested Provides would suffice for exact
> kernel module dependencies.
"exact" is the easy case, set up a Provides: and Requires: dependency match on,
say, the MD5 of /boot/vmlinuz.
What's trickier is the fuzzy match across a range of kernels that might
reasonably run a given build of a module.
If insmod can figger out that problem at run time, then rpm can figger
out the same problem at build/install time.
Assuming that insmod doesn't change, of course. ;-)
73 de Jeff
--
Jeff Johnson ARS N3NPQ
jbj at redhat.com (jbj at jbj.org)
Chapel Hill, NC
More information about the devel
mailing list