Le 2022-06-22 19:14, Thorsten Glaser a écrit :
With these changes I think it's now possible to detach the sysvinit
script
into an independent package (tomcat9-sysvinit?) enhancing tomcat9.
*WHY*?
The remaining changes do not change the way it is run under systemd
AT ALL.
Because separate packages means separate responsibilities. I'd like not
to maintain again sysvinit scripts in any Java package, we don't have
the time for this (we barely keep up with the Java and toolchain
upgrades).
That said, I'm fine with applying some reasonable changes that ease the
use of sysvinit (like the logger change and the switch to the standalone
systemd-sysusers).
Having an extra binary package just for a handfull of scripts is
absolute overkill and ftpmasters from upon that, too.
If the number of packages matters, I've removed several unused
lib*-java-doc
packages recently, so one more package for the Tomcat init script isn't
really
an issue, the net change for the Java packages is negative.
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.
Emmanuel Bourg
__
This is the maintainer address of Debian's Java team
<https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>.
Please use
debian-j...@lists.debian.org for discussions and questions.
