Comment # 14 on bug 1194723 from Michal Suchanek

So where are we with this?

IIRC the dkms service was required on Debian as well - the modules would
sometimes not build or build for a different kernel, and would rebuild during
boot to be loadable on the booted kernel.

It would be nice to build them in advance but even on Debian (the d in dkms
stands for Debian IIRC) this is best effort.

Adding a posttrans for kernel-binary would cover only some cases. We would need
one for kernel-binary-devel as well which is not in s-m-t IIRC. 

There is also the question what is specifically passed to the kernel.d scripts.

Does it get just called once when something with kernels changes, or is it
called for each kernel added/removed with some specific arguments that describe
the event?