* On 10/9/24 14:41, Andrei Borzenkov wrote:

You assume that KMP *packages* are created on the end system. They are not.

Oh, yes, I did. If they are not, then there's no way to track the generated modules from a package management perspective and neither auto-cleanup nor manual cleanup via the PM is possible. Hence, users will (currently) have to remove obsolete kernel modules completely manually.

They probably could be. That would indeed solve this issue at the expense of pulling in even more dependencies (each end system will need rpmbuild with whatever it requires and BuildRequires for KMP).

That shouldn't be an issue. Since the modules are already built from source, the list of additional dependencies would probably be slim to non-existent.

Besides I am not sure that RPM allows nested installation of package from within installation of a different package.

This, however, is a great concern. RPM is not re-entrant and while installing a different package in a %posttrans scriptlet might work by sheer luck, there is enough potential for breakage that I wouldn't even try that. Mihai