[pkg-lighttpd] Bug#846299: seems to work without the dependency for me

Adam Borowski kilobyte at angband.pl
Fri Dec 2 21:08:19 UTC 2016


> lighttpd 1.4.39-1 depends on lsb-base (>= 3.2-14) | systemd (>= 29.1)
>
> while lighttpd 1.4.43-1 depends on lsb-base AND systemd,
> is it intentional?

While my initial reaction was to recompile lighttpd without systemd ballast
(as I maintain a desystemdized set of packages), it turns out no such
treatment is needed: there is no runtime dependency on any systemd
components at all.  I've just rebuilt the package with no changes other than
this spurious dependency dropped, and with (very superficial) testing it
appears to work fine.

I see no mention in the changelog why such a change was done, the only thing
that seems remotely connected is:
# * Use upstream's systemd service file.

If that's the rationale, it's pointless: lighttpd ships a proper init script
so it works on (paraphrasing Marco d'Itri) non-toy inits, and systemd
systems, which indeed need systemd to use the service file, already do have
systemd installed.

And in case you intended this as a versioned dependency, even oldstable has
systemd 44 which satisfies >= 29.1.

Dropping this will also make the package installable on kfreebsd, which, the
last time I checked, didn't have systemd.


Meow!
-- 
The bill declaring Jesus as the King of Poland fails to specify whether
the addition is at the top or end of the list of kings.  What should the
historians do?



More information about the pkg-lighttpd-maintainers mailing list