On Wed, Jan 21, 2009 at 07:28:26PM +0100, Kurt Roeckx wrote: > All policy seems to have to say about this is: > Packages that include daemons for system services should place scripts > in `/etc/init.d' to start or stop services at boot time or during a > change of runlevel. These scripts should be named > `/etc/init.d/<package>' > > It's only a should and not a must. > > But it has also been pointed out that this is what administrators > expect. And I see no good reason not to provide that interface > to our users. Only providing the runit version seems to cause > more problems for the users that are not familiar with it. It > could even be argued that if you provided an init.d script you > would have less bug reports. > > I would recommend putting the init script in the same binary package > as the daemon itself. Having it in an other package will most likely > result in the service being stopped and not started again on upgrades. > > And I don't think having a new source package just to provide an init > script is a good idea Actually it does provide an init binary. It is not a script, though (and thus it does not contain any LSB headers). It might be silly to insist on a simple script doing an exec on sv, the program through which services provided through runit can be managed. Gerrit is still unavailable until the end of January. Kind regards, Philipp Kern -- .''`. Philipp Kern Debian Developer : :' : http://philkern.de Release Assistant `. `' xmpp:phil@0x539.de Stable Release Manager `- finger pkern/key@db.debian.org
Attachment:
signature.asc
Description: Digital signature