Bug#591791: extend init.d policy to permit upstart jobs and describe their use

[Jonathan Nieder <jrnieder@gmail.com>]

Jonathan Nieder wrote:

> In an ideal world, (i) would be enough [since it determines the
> behavior] and packagers could experiment

Just to be clear: I was reading from the point of view of what a
packager of an ordinary daemon needs to do.  But the requirements on
init systems are important, too[1].  Sorry about neglecting that.

[1] Examples: to what extent an init system is allowed to ignore
init scripts provided by other packages when it provides its own
native equivalents.