we have some scripts that may need to be run after etc-update is executed ... for example, any files installed into /etc/modules.d/ or /etc/modprobe.d/ should have `update-modules` run afterwards or after /etc/ca-certificates.conf is updated, update-ca-certificates should be executed
I assume you want this for all config file managers, not just etc-update, right?
the immediate need was for etc-update, but if you want to make it extensible and make it agnostic of the utility, that's fine
(In reply to comment #2) > the immediate need was for etc-update, but if you want to make it extensible > and make it agnostic of the utility, that's fine > A daemon using inotify maybe?
(In reply to comment #3) > > A daemon using inotify maybe? > Would have the benefit of catching changes done outside of etc-update too. Then it could optionally have a dbus based API to ask for confirmation from the user on running the tool.
ugh, i see that as a death spiral
Petteri: Your thinking wayyyy to high level on this one right now. The tool we need is much lower then that. Granted, if you wanted something like this, I'm sure we could make some hooks in there to call some bash D-Bus bindings to notify stuff like gnome-system-tools/backends. vapier: This is exactly what we need. Great idea.
i think for most things now, people have converted to .d dirs so fragments can be installed without having to generate a single config file. certainly for the modules/modprobe stuff, that's what we do.
