Hi All, Recently the CRUX Development Team has introduced a new port into "core" ports of CRUX, a tool from Debian called "start-stop-daemon". For whatever reason this tool was introduced a) It was now discussed here and b) brought in new breaking changes. I think it's important to discuss any major changes that affect the architecture and user experience of CRUX with the community. 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. But the Port guidelines say not to do this which I think in this case is a bit silly or at least ambiguous. So all this aside... Let's discuss what we can here... Do we need to update our Polices? I think so. Should we list run-time dependencies that are not linked against? I definitely think so - otherwise you end up with a potentially broken system. 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? Your faithfully, James Mills (a long time CRUX user) James Mills / prologic E: prologic@shortcircuit.net.au W: prologic.shortcircuit.net.au