![](https://seccdn.libravatar.org/avatar/9435667f7160374bc34a8600b686aecd.jpg?s=120&d=mm&r=g)
On Mon, Jun 14, 2021 at 10:00 AM Martin Wilck <martin.wilck@suse.com> wrote:
On So, 2021-06-13 at 09:29 +0300, Andrei Borzenkov wrote:
On 07.06.2021 23:09, Martin Wilck wrote:
You probably know, but as some readers who may not: weak-modules2 is part of the suse-module-tools package. I guess one *could* try to use it for DKMS-built modules. I've never tried.
It has different API than weak-modules (that was removed from suse-module-tools. Author sounds familiar ...)
weak-modules has been moved to suse-module-tools-legacy, which is still available (*). IIRC weak-modules had no users under (open)SUSE since
Well, I was not aware of weak updates support in DKMS either.
Code 10. suse-module-tools is a basic package, I try to keep it small and only ship the necessary tools.
So far I thought that weak-modules2's functionality was a superset of weak-modules. But I confess I didn't explore in depth. Can you explain what it's lacking?
It is just different calling conventions. dkms does list_each_installed_module "$module" "$kernelver" "$arch" | ${weak_modules} ${weak_modules_no_initrd} --add-modules and weak-modules2 does not have --add-modules option nor does it accept a list of modules on stdin.