Apparently sysvinit scripts must be retained anyway for a smooth migration to jessie; also for easy backporting of jessie packages to wheezy, and maybe other reasons. Non-Linux ports are likely to use those SysV init scripts, though we might invoke them from something other than sysvinit.
I know some maintainers would like SysV init scripts to disappear, but the earliest I think that can happen for existing packages would be jessie+1. In that case, we should try to plan for a similar migration from jessie to jessie+1. It's difficult to predict so far ahead, but if it will be a migration to OpenRC, maybe jessie should try to have OpenRC already in place, so that it will be able to use jessie+1's runscripts when they appear and be able to shut down cleanly when SysV init scripts are gone. (I think Thomas was describing the same situation in the context of sid) Regards, -- Steven Chamberlain ste...@pyro.eu.org -- To UNSUBSCRIBE, email to debian-devel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5303f898.7070...@pyro.eu.org
