on Tue, 29 Oct 2013 15:08:01 -0700 Russ Allbery wrote: > However, I, as a packager, want to stop writing and maintaining SysV init > scripts because they're awful.
I didn't really expect this. I'd assumed until now that most maintainers would be concerned that existing init scripts don't work properly on the new system, and having to fix them. But you actually want to do that, and get rid of SysV init scripts too. We now have at least one new option available to the ports which is OpenRC[0]. If for example it was supported alongside systemd (or substitute Upstart here if you prefer), each package's maintainer could: * keep their SysV init scripts and let both init systems use them * write a new systemd unit but keeping the init scripts for OpenRC * write a new OpenRC configuration (I don't even know what that looks like yet), keeping the SysV init scripts for systemd * write a new systemd unit and an OpenRC configuration, can then drop the SysV init scripts * write a new systemd unit and specifically depend on systemd, perhaps leaving the package unavailable to ports But I don't suggest this is only for the benefit of ports. Even Linux users have spoken concerns about systemd specifically. If it were introduced, I'd like to have a lightweight and less controversial alternative, and it's really convenient if it is portable. [0]: https://lists.debian.org/5270b735.8010...@debian.org 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/5270fce2.3030...@pyro.eu.org
