the 'at-boot' package method: a change of direction

Folks, there's been a dubious idea floating about (courtesy
of me) that any ARK package that needs something done at
boot time (e.g. the openssh packages wants sshd started) can
simply heave in an 'at-boot' method.

You set up an init.d script to do

   ark package at-boot --host=. ALL--ALL

and that will start *all* your ARK-controlled stuff; if
you've put in <dependency .../>'s, it will even do them in
the right order!  As packages come and go, you don't have to
change your init.d scripts -- the above takes care of it.
This is cool.

But it means you don't have per-package init.d scripts that
you can use ad-hoc-ishly.  You can't do

    cd /etc/init.d
    sudo ./sshd stop && sudo ./sshd start

for example, because there *isn't* an sshd init.d script.

I therefore suggest that (sidai-ish) packages with boot-time
pretensions should generate a normal start/stop init.d
script, perhaps in their post-install-bits method.

The 'at-boot' method could live on, but it would just invoke
"/wherever/init.d/blah start".

Seem reasonable?

Will