Arturo Borrero González:
* systemd is starting to drop support for some sysvinit mechanisms
[https://sources.debian.net/src/systemd/231-4/debian/systemd.NEWS/]
Don't employ such thinking. It is a mistake; in two ways no less.
Close on the heels of the Debian Technical Committee's decision about
systemd being the default, one Debian package maintainer thought as you
are thinking. If systemd was the now the default, xe could drop the van
Smoorenburg rc scripts from xyr packages. A furore resulted, the
outcome of which has already been mentioned in this discussion.
You also need to look at what Debian systemd is dropping support for.
Is your rc script a run-level "S" script? No, it is not. What makes you
think that what is being announced for systemd 231 on Debian even
applies to your package? It is a mistake to make superficial and glib
analyses that systemd not supporting a very specific thing is somehow
systemd not supporting anything at all; especially in light of the fact
that the systemd developers have had a list of "Oddball things that you
can actually do with rc scripts that systemd isn't going to support."
for several years, now. Ironically, not supporting run level "S" has
been on that list for a long time. What's happening is actually that
Debian's special exception is being taken away.
* https://wiki.debian.org/Teams/pkg-systemd/rcSMigration
* https://www.freedesktop.org/wiki/Software/systemd/Incompatibilities/
* https://jdebp.eu./FGA/systemd-documentation-errata.html#SingleUserRunLevel
