phosphor-fan/phosphor-power: disable automatic service start

The systemd.bbclass will now attempt to automatically enable any
service found in the SYSTEMD_SERVICE variable, which systemd-v259
treats as a failure for template service files (since it doesn't
know what the appropriate argument is).  This unfortunately collides
with behavior in obmc-phosphor-systemd.bbclass that uses the
SYSTEMD_SERVICE variable to know which services to auto-install.

The ideal behavior at this point is probably to deprecate
obmc-phosphor-systemd.bbclass and move all recipes off of it, and
leverage the behavior built into systemd.bbclass directly.  This
works for services that are non-templated and/or only need to be
installed into the multi-user.target, but needs more experimentation
for install into non-default targets.

For now, set SYSTEMD_AUTO_ENABLE to `disabled` for specific packages
that install a template service and are already handled by
obmc-phosphor-systemd.

Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I31b6256a619bd56d0789ad34a8432b75d8623a2a

0 files changed, 0 insertions, 0 deletions