sysvinit should depend on initscripts for a functional /lib/sysvinit/init

[Josh Triplett]

On Sun, Jul 17, 2016 at 03:07:23PM -0700, Josh Triplett wrote:
> On Sun, Jul 17, 2016 at 11:30:26PM +0200, Michael Biebl wrote:
> > Am 17.07.2016 um 23:17 schrieb Josh Triplett:
> > > On Sun, Jul 17, 2016 at 11:05:09PM +0200, Michael Biebl wrote:
> > >> If you have systemd-sysv installed and you want to try sysvinit-core,
> > >> you install the package and you get a fallback grub menu entry for
> > >> systemd (unless you also purge the systemd package). So it is still
> > >> easily possible to switch between the two init systems.
> > > 
> > > Only by having sysvinit installed as the default init system.
> > > Previously, it was possible to have systemd as the default (matching the
> > > Debian default) but still use sysvinit.  Now, it seems like sysvinit
> > > will become the only init system in Debian that *can't* boot without
> > > being the default.
> > 
> > Which other init systems do you have in mind which would allow that?
> 
> systemd.  upstart, until it was removed.  runit.  openrc (which can't
> coexist with sysvinit because it replaces sysv-rc, but which doesn't
> have to be the default unless sysvinit does).

One thing I should mention here: I'm not a user of any of these init
systems (including sysvinit).  I personally would have no objection to
dropping any or all of them entirely.  So, if no interest materializes
in maintaining this support, I certainly won't push for it.

- Josh Triplett