On Wed, Sep 09, 2020 at 11:33:18AM +0200, Stefan Seyfried wrote:
Am 08.09.20 um 18:36 schrieb Hans-Peter Jansen:
Can't halp you with your questions, sorry, but this reminds me of something, that I wanted to ask: for what reason does the kmp package rebuild the initrd?
That's part of the kmp packaging macro magic, not much the kmp packager can do about it.
There is the possibility of doing crazy ugly hacks like
%define regenerate_initrd_posttrans /bin/true\ %{nil}
but a bug / feature request against kernel-macros package to give kmp packagers an easy and documented way to say "this module will not end up on initrd" would be better :-)
But can you ever be sure that it definitely cannot end up in initrd? How do you e.g. prevent user from putting it into INITRD_MODULES explicitly? I'm afraid the only safe way would be a dracut feature that would let you check if it would put a module into initrd based on current configuration and dependencies. Michal Kubecek -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org