On Sun, 22 Feb 2015 20:04:24 +1000 James Mills wrote:
Introducing start-stop-daemon and then changing openssh's rc script (/etc/rc.d/ssh) to use /sbin/start-stop-daemon and not listing start-stop-daemon IHMO is wrong.
IIRC, as a general rule, it is mandatory/really recommended to have all core ports installed on a system, so converting openssh rc script to use start-stop-daemon and not listing it as a run-time dependency is not a problem, since its part of the core, so must be installed. If you want a working system, that is :)
Should we list run-time dependencies that are not linked against? I definitely think so - otherwise you end up with a potentially broken system.
Examples?
Lastly, Why are we introducing (already have) start-stop-daemon from Debian's ecosystem? What are we trying to solve with this tool that we can't otherwise solve in other ways or have issues with certain softwared fixed upstream?
From the post to the ML that introduced the change: "We encourage all port maintainers to use start-stop-daemon in their rc scripts. This will improve the scripts a lot without the need for complex shell scripting." I find it is much easier to use upstream provided init/rc script for Debian and modifying it, if needed, than starting from scratch, when I am making a port. Pedja