On Tue, Feb 04, 2025 at 06:48:39PM +0100, Marco Ricci wrote: > Thus wrote Helmut Grohne: > > I think we could reasonably remove the entire dependency instead. > > Whilst lighttpd integrates with systemd, there are more ways to run it > > (e.g. in an application container it may be started directly). Other > > packages such as apache2 do not depend on systemd-sysv either. As > > a result, I recommend dropping the dependency. > > I agree from a practical standpoint -- lighty works very well as > a managed service à la runit, without the SysV init machinery or > scripts. But deciding on whether this is reason enough to drop the > dependency altogether appears (to me at least) to be more of a policy > question than a technical question. And I can't really comment usefully > on those.
lighttpd integrates with multiple system configurations. If your system has systemd, then when you install lighttpd you'll use lighttpd.service. If your system has lsb-base, then when you install lighttpd, you'll use lighttpd.init. lighttpd does not require a specific system configuration. Thank you, Helmut, for the background and for the recommendation.
