certificates: clean up config recipes

Since the config recipe packages will create symlinks to the certificate
manager template, RDEPEND rather than RRECOMMEND on the certificate
manager package (which provides the template).

Avoid obmc-phosphor-systemd.  Enabling systemd units is the realm of
packaging scripts and the SYSTEMD_LINK feature in obmc-phosphor-systemd
implements this incorrectly.  Just directly code install, pkg_postinst
and pkg_prerm here rather than trying to fix obmc-phosphor-systemd - the
extra indirection is more harmful to ease of comprehension for seasoned
Yocto developers than the couple of lines of code it saves.

Change-Id: I69c1a2f7978909c93c122da2a729f2dfec77562e
Tested: Built witherspoon image and verified rootfs unchanged.
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
4 files changed
tree: a902f7020bcb7876838c7e4c94d7b84fee6969e5
  1. aspeed-layer/
  2. classes/
  3. conf/
  4. nuvoton-layer/
  5. recipes-connectivity/
  6. recipes-core/
  7. recipes-devtools/
  8. recipes-extended/
  9. recipes-phosphor/
  10. recipes-protocols/
  11. recipes-support/
  12. recipes-textproc/
  13. COPYING.apache-2.0
  14. COPYING.MIT
  15. LICENSE
  16. MAINTAINERS
  17. README.md
  18. recipes.txt
README.md

OpenBMC

meta-phosphor is the OpenBMC layer. This layer should be included for all OpenBMC systems. The OpenBMC layer contains content which is shared between all OpenBMC systems.