All packages have already sysvinit scripts, what is the problem to have both systemd and sysvinit scripts in the package? Other system can be easily supported by contributors who want to run the package on particular init system - like me, I am using 'runit' for init system..
.. and for people that don't like the desing of systemd and don't want to use the LARGEST security risk installed by default in many years on Debian???
I am exploring some other linux distributions as well as BSD. http://voidlinux.eu/ seems pretty nice but still in early stage of developement. It uses 'runit' as init system, packaging system si something like NetBSD pkgsrc. Other option is to replace all my linux boxes wth NetBSD (as I am using it since 2.0 version):)
Debian is dying, I can clearly see this now and I wonder when stupid people took over leadership of Debian???
I still have a lot of servers with Debian Squeeze and I am not planning to upgrade them. This is the last version of Debian that is usable for server. There will be distributions without systemd I hope (like voidlinux which is still in early stages of developement)
Things will go just like in MS Windows.
Systemd as a supervision daemon - it is ok, but replacing the whole init system/login/logging/whatever is the thing that scares me off.