init script generators ( was: Re: proper handling of communication channels in debian)

[Erich Schubert]

Hi,
> > The postinst of the package shipping the meta-init-script is more
> > appropriate.
>
> Why? AFAIU, for the dpkg-trigger approach to work, init packages just need

Because it's essential for system operation, and dpkg-trigger doesn't exist yet.
I'm fine with migrating this to dpkg-trigger once that is a key part
of Debian, but there is a couple of things that should be migrated
then (e.g. the menu system). Having the transformation script run only
once at the end of the install offers little benefits here, since it
will likely only process the new files anyway.
This is different than with e.g. update-menus, which probably
processes all menu files on each run. Or scrollkeeper and other
indexing stuff.
This might be different with some init systems that compute
dependencies on install time though.

But I'd wait for a generic dpkg-trigger migration to happen. The
current approach would work on a etch system (and probably back to
woody), and thus offers a clear and reliable upgrade path. And I'm all
in for avoiding potential upgrade issues.

best regards,
Erich Schubert
--
    erich@(mucl.de|debian.org)      --      GPG Key ID: 4B3A135C    (o_
  To understand recursion you first need to understand recursion.   //\
  Wo befreundete Wege zusammenlaufen, da sieht die ganze Welt für   V_/_
        eine Stunde wie eine Heimat aus. --- Herrmann Hesse