On Tue, Jun 16, 2015 at 11:09:43AM +0200, Anto wrote:
>
>
> On 16/06/15 10:58, Arnt Gulbrandsen wrote:
> >Anto writes:
> >>Yes. I almost have everything to start trying to build epoch package,
> >>*except* one important point that I have been asking for. That is the
> >>mechanism to trigger an action to automatically update epoch.conf and
> >>start the daemon when we install all packages with daemons that need to
> >>be started/stopped at boot/shutdown time, *without* including epoch
> >>specific files into those packages. So what I am basically looking for
> >>is totally different approach than what Debian based distros have been
> >>doing for other init systems, so that we don't need to patch all of
> >>those packages with epoch specific files and re-build them.
> >
> >You have code that rescans /etc/init.d and parses those LSB-Foo-Bar
> >comments, is that right? If so, you have three options:
> >
> >1. Piggyback on someone's post-install hooks.
> >2. Run inotify() in a patched epoch and watch for file creation in
> >/etc/init,d
> >3. Invent a new hook that lets you process ALL dpkg -i calls.
> >
> >Pick your poison.
> >
> >Arnt
> >
>
> Thanks a lot Arnt,
>
> Option 1 is definitely not what I am looking for. Option 2 looks to be the
> most elegant solution, assuming that all packages will still generate their
> sysvinit files on /etc/init.d.


If you were open to option 1, you could install your own update-rc.d
if you conflicted with sysvinit.

The init scripts are *not* generated: they are config files that are
included in the package, but will not be replaced if modified unless
you specify to replace them.
But watching for file creation seems like a case of refusing to work
with the package manager.

For option 3:
https://wiki.debian.org/DpkgTriggers


HTH,
Isaac Dunham