tree 3c3b43c3b67d3d4fece4982179195d8fd43a7bd1
parent 24be2dfa81d083ab315c2cf290b3b32a2d9e18d1
author Brad Bishop <bradleyb@fuzziesquirrel.com> 1600199188 -0400
committer Andrew Geissler <geissonator@yahoo.com> 1600907999 -0500

meta-phosphor: add a base image recipe

Much like core-image-base, add a base OpenBMC image
obmc-phosphor-base-image.

This is essentially CORE_IMAGE_BASE_INSTALL +
packagegroup-obmc-apps-extras (which is empty by default).

At time of writing, obmc-phosphor-base-image is an abstract thing and
doesn't make any specific statement about content.  The initial intent
is twofold:

1 - Provide a base image upon which space constrained users can "build up"
  their image content by appending to IMAGE_FEATURES in place of the
  current practice of "tearing down" obmc-phosphor-image by _remove-ing from
  IMAGE_FEATURES (The Yocto layering implementation prefers appending over
  _remove-ing for maximum layer compatibility).

2 - Over time, a carefully curated set of IMAGE_FEATURES would be added
  (there aren't any at the moment) that provides content that most
  users would expect by default.

(From meta-phosphor rev: fb768573bc58d020b63dba323cb0eb3afafd5e6d)

Change-Id: Id3b15ffd8084298a4784ad1b3c4004b2cb2f73e4
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>