I don't know how to differentiate between if `manual_add_modules` was called by a script in /usr/share/initramfs-tools or from outside.
The only safer solution that I can come up with: Keep `manual_add_modules` as it is and introduce a new function (e.g. `manual_stage_modules`) that introduces the new behavior. The consumers in initramfs-tools will switch to the new function. Then the worst offenders (that call `manual_add_modules` many times) need a SRU to change from `manual_add_modules` to `manual_stage_modules`. initramfs-tools in oracular would get a `manual_stage_modules` function as well for easier upgrades.
Then there will be only a slight risk left: Custom scripts that rely on other hooks (that switched from `manual_add_modules` to `manual_stage_modules`) to have the kernel modules copies to $DESTDIR.
I don't know how to differentiate between if `manual_ add_modules` was called by a script in /usr/share/ initramfs- tools or from outside.
The only safer solution that I can come up with: Keep `manual_ add_modules` as it is and introduce a new function (e.g. `manual_ stage_modules` ) that introduces the new behavior. The consumers in initramfs-tools will switch to the new function. Then the worst offenders (that call `manual_ add_modules` many times) need a SRU to change from `manual_ add_modules` to `manual_ stage_modules` . initramfs-tools in oracular would get a `manual_ stage_modules` function as well for easier upgrades.
Then there will be only a slight risk left: Custom scripts that rely on other hooks (that switched from `manual_ add_modules` to `manual_ stage_modules` ) to have the kernel modules copies to $DESTDIR.