![](https://seccdn.libravatar.org/avatar/f0b862ee805990499445d7d2b8834647.jpg?s=120&d=mm&r=g)
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 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? Regards Martin (*) I've indeed considered ditching it for good. I was unaware of the fact that people are still using weak-modules.