Le 23/06/2022 à 00:52, Emmanuel Bourg a écrit :

To avoid the proliferation of sysvinit script packages the best approach
would be to group the scripts into a common package (maybe using a trigger
to install the script when a supported daemon is installed on the system).
This would lift the burden of maintaining these scripts off most DDs and
delegate the work to a small set of dedicated maintainers, properly
optimizing and harmonizing these scripts.

It appears that this idea has been implemented last year with the orphan-sysvinit-scripts package, under the Debian sysvinit maintainers umbrella. It was released with Bullseye and already contains an init script for tomcat9.

So at this point, we have a tomcat9 package with a systemd service file, which plays nice on systems without systemd, and can be started with sysvinit by installing an extra package.

Could we agree this is a fair compromise, compliant with the result of the GR on init systems, and move on?

Emmanuel Bourg

Reply via email to