[FEATURE] Consider making use of and expanding the needsreboot functionality

[joebonrichie]

Proposal

There is some needsreboot functionality in eopkg where if a installed package has the correct marker in it's history section then that package will be added to /var/lib/eopkg/info/needsreboot. Unfortunately, though the rest of the functionality probably exists in comar to make use of it which we do not use.

To mark a package as needing reboot then the action must be specified in the history section of the contained metadata.xml file.

<Requires>
    <Action package="zed">systemRestart</Action>
</Requires>

e.g.

        <History>
            <Update release="87">
                <Date>2025-07-16</Date>
                <Version>0.195.3</Version>
                <Comment>Packaging update</Comment>
                <Name>Joey Riches</Name>
                <Email>josephriches@gmail.com</Email>
                <Requires>
                    <Action package="zed">systemRestart</Action>
                </Requires>
            </Update>
        </History>

Upon installation this package will then be added to /var/lib/eopkg/info/needsreboot

The existing apis will also see that that package needs reboot

>>> pisi.api.list_needs_reboot()
['zed']

Unfortunately thats where the functionality ends.

Some external contained system service may be able to make use of this by watching the file and clearing it after a reboot.

Use cases

Notify the user when the system needs rebooting after package upgrades e.g. kernels, mesa, etc.