Hi folks,
I'm trying to build an RPM for a kernel module that can rebuild itself when the kernel is upgraded. Using a trigger is the obvious choice, but the process would be made much cleaner if the trigger script could determine to which version the triggering package is being upgraded.
Is there a sanctioned way of doing this?
With rpm-4.2.1, you should be able to access the database from the trigger script, so all that is needed
is extracting the correct package from the results of a query.
Note that 2 kernel packages will be installed when the trigger runs, rpm does install before erae.
A more portable solution will require you to script your own test.
73 de Jeff
_______________________________________________ Rpm-list mailing list Rpm-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/rpm-list
