RPM dependency rationale (and kernel packages)?

Nils Philippsen nphilipp at redhat.com
Wed Aug 20 18:50:31 UTC 2003


On Wed, 2003-08-20 at 19:58, Jeff Johnson wrote:

> For (a totally artificial and probably insane) example, let's say a
> kernel module was built against some kernel on a build machine and
> needed the symbol (early in System.map was the criteria of choice)
> 	c0100218 T stack_start
> A little bit of sed magic might automagically generate a dependency
> like
> 	Requires: ksym(stack_start)
> 
> Then the magic construct "ksym(...)" could grovel through the System.map
> (or whatever insmod uses these days) at install time to check to see
> whether yes, indeed, there was an already installed kernel that might
> satisy each and every symbol.

Or could be checked against an (equally automatically generated)

Provides: ksym(stack_start)

(which admittedly would cause quite some bloat in /var/lib/rpm).

Though that wouldn't help if the required symbols are scattered over a
number of kernels (yes, this is an improbable scenario).

If we had such a scheme, the user should be able to select which
requirements to show with '--requires' (unless he's a fan of sifting
through pages of output).

Nils
-- 
     Nils Philippsen    /    Red Hat    /    nphilipp at redhat.com
"They that can give up essential liberty to obtain a little temporary
 safety deserve neither liberty nor safety."     -- B. Franklin, 1759
 PGP fingerprint:  C4A8 9474 5C4C ADE3 2B8F  656D 47D8 9B65 6951 3011
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
Url : http://lists.fedoraproject.org/pipermail/devel/attachments/20030820/540f38f0/attachment-0002.bin 


More information about the devel mailing list