[systemd-devel] /usr/lib/systemd/*.wants vs. Wants in unit definition

[Andrei Borzenkov]

On Mon, Jun 6, 2016 at 2:26 PM, Martin Pitt <martin.pitt at ubuntu.com> wrote:
> Andrei Borzenkov [2016-06-06 13:55 +0300]:
>> What is advantage in having static *.wants etc directories in
>> /usr/lib/systemd vs. Wants etc directives directly in unit definition?
>> They complicate troubleshooting (you no more have complete definition
>> by looking just at unit source), they complicate building (extra steps
>> to install them); what are they good for?
>
> These are much simpler to ship in packages than shipping a
> foo.service.d/mywants.conf with "Wants=".


Sorry I had to be more clear. What is advantage of shipping them in
systemd? Systemd has well defined early boot services that are always
needed. Why they are shipped as links instead of actually expressing
those mandatory dependencies in unit definitions themselves?