systemd: no installation in templated targets

Upstream yocto introduced a change via e510222 (systemd-systemctl:
fix instance template WantedBy symlink construction).

This fixes a bug that we in OpenBMC had been taking advantage of in that
we were able to document our templated target dependencies without it
actually doing anything. The real installation of services within
targets occurs in our bitbake recipes due to the complexity of chassis
and host instances on a per machine basis.

Leave the dependency information in the service files but comment them
out. It's useful to be able to look at a service and understand which
targets it's going to be installed into by the bitbake recipes.

Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
Change-Id: I58b4e0f280bcf0268a737aec2613f2d6ca8c8eba
13 files changed
tree: 7d226f2c4e2beaa0c4c7445a3e4be7dd21538ee7
  1. extensions/
  2. procedures/
  3. service_files/
  4. test/
  5. .clang-format
  6. .gitignore
  7. .shellcheck
  8. cfam_access.cpp
  9. cfam_access.hpp
  10. ext_interface.cpp
  11. ext_interface.hpp
  12. filedescriptor.cpp
  13. filedescriptor.hpp
  14. LICENSE
  15. meson.build
  16. meson_options.txt
  17. nmi_interface.cpp
  18. nmi_interface.hpp
  19. nmi_main.cpp
  20. OWNERS
  21. p10_cfam.hpp
  22. p9_cfam.hpp
  23. proc_control.cpp
  24. README.md
  25. registration.hpp
  26. targeting.cpp
  27. targeting.hpp
  28. temporary_file.cpp
  29. temporary_file.hpp
  30. util.cpp
  31. util.hpp
README.md

Contains procedures that interact with the OpenPower nest chipset.

To Build

To build this package, do the following steps:

    1. meson builddir
    2. ninja -C builddir

To build with phal feature:
    1. meson builddir -Dphal=enabled -Dopenfsi=enabled
    2. ninja -C builddir

To clean the repository run `ninja -C builddir/ clean`.