On Tue, May 24, 2022 at 6:49 AM <
karl@aspodata.se> wrote:
Is there some hook to emerge I can use where I can attach some code to
run tests after each individual package when doing emerge @world ?
So, Portage has hooks, and that would work for any file being
installed normally (so would config protection and that would be a
much easier solution).
There are a couple of problems though:
1. The only package I'm aware of that directly touches /dev is
static-dev (which I hadn't even heard of until you mentioned it). It
uses a post-install hook to create device nodes, so there is no
opportunity to inspect anything before /dev is modified. This isn't
the normal way to install files, but of course it isn't installing
normal files.
2. I think it is very unlikely that a package is directly modifying
/dev. It seems more likely that a package is installing some daemon
that gets run as root and then it modifies /dev, maybe on your next
boot. Obviously if you install something like udev you'd expect to
end up with /dev getting modified when it runs. Again, there is
nothing for a hook to detect.
Having a backup (it is static after all), and something like a
read-only mount might be your better solutions, if you really want a
static dev, or maybe marking files as immutable or something. (You
might want to test that - I am assuming you could still write to a
device node on a read-only filesystem but it isn't like I've tried. I
don't think there is anything special about /dev so you could just
create a device node in some other read-only filesystem and test it
out.)
If you do find a random package touching /dev I think most here would
be pretty interested, as that seems rather bizarre.
--
Rich
--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)