On Monday 06 of February 2012 12:51EN, Sven Burmeister wrote:
And since you and those complaining about systemd would not use systemd anyway, why do you care whether there are sysvinit scripts removed for a systemd environment?
If you come up with a maintainer include the sysvinit scripts in the sysvinit package.
They wouldn't be removed from "a systemd environment" as they are not in one. These scripts (most of them) are part of the packages relevant services are implemented by. Which is kind of necessary because if you want them in sysvinit package, you can have only a certain fixed set of scripts in it, not all scripts for all services you could possibly have in the system. It is similar to the dilemma whether AppArmor profiles should be in apparmor-profiles or in the relevant packages with the programs; the difference being that a daemon is fully usable without its AppArmor profile.
So what are you really planning to do is (1) order all service package maintainers to include a systemd unit file and (2) forbid them to include a LSB compliant init script.
Michal Kubeček