Comment # 32 on bug 1224773 from Alberto Planas Dominguez

(In reply to Ignaz Forster from comment #31)

> @Alberto: On a first glance I couldn't find any RPM macro integration so
> that a RPM package calling %regenerate_initrd_post would trigger the initrd
> rebuild on a systemd-boot system. Am I missing something, or do we still
> have to implement this?

regenerate-initrd-posttransaction script has been updated here:

https://github.com/openSUSE/suse-module-tools/pull/103

It is still under review, and requires a new plugin in sdbootutil, that is
here:

https://github.com/openSUSE/sdbootutil/pull/92

This plugin is a tukit (transactional-update) plugin, using a new mechanism
implemented here:

https://github.com/openSUSE/transactional-update/pull/122

So all has been implemented, and all of them are waiting reviews (except
sdbootutil#92 that I reviewed myself :P)

The new mechanism should be working as this:

1) tukit can execute plugins in a -pre / -post fashion similar to snapper, for
each verb like "call", "callext", "open", "abort". The exact list is documented
in transactional-update#122

2) sdbootutil provides a plugin for callext-post, that will inspect
$bind_dir/run/regenerate-initrd.  If it is present inside the transaction it
will be copied outside in the host /run

3) regenerate-initrd-posttrans is now aware of transactional systems with a
separate /boot partition (that is the case for FDE when using systemd-boot or
grub2-bls) If detected and the scriptlet is called _inside_ the transaction it
will do nothing, as this would require changing something _outside_ the
transaction (the risk of that is that you can see initrds that are not attached
to any transaction, for example)

4) sdbootutil provides the old snapper plugin that is executed once the
transaction is closed and available, and will call regenerate-initrd-posttrans
if the host /run contains the regenerate-initrd/ directory, but now from
outside the transaction