meta-phosphor: temp remove PV for git recipes

In the five step sequence of transitioning an unversioned recipe to
a versioned one, PV cannot be explicitly set to 1.0+git${SRCPV} set
until the last step.

With PV set, _both_ the unversioned recipe and the versioned recipe
end up with PV = 1.0 and bitbake will continue to use the unversioned
file.  This means that when the unversioned bbappends are removed in
step 4, the bbappend does not occur.

This commit can be reverted once the five step process is complete.

For reference, the five step process is:

1.
Create a temporary recipe symlink:
foo.bb -> foo_git.bb

This results in two available PVs for foo: "1.0" (the bitbake default
for unversioned recipes) and "git".

Further, set the preferred version for foo to "1.0" in the distro
configuration otherwise bitbake will choose PV = "git" and existing
(unversioned) bbappends will not apply and the build will break.

2.
Create a temporary bbappend symlink:
foo.bbappend -> foo_%.bbappend

This allows the manual override of the preferred version introduced in
step 1 to be removed from the distro configuration.

3.
Remove the preferred version override introduced in step 1 from the
distro configuration.  At this point the versioned recipe is now being
used.

4.
Remove the unversioned bbappends.

5.
Remove the unversioned recipe.

Change-Id: Ifb4efd5fcc29e958267243964085ab61aa3ca828
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
9 files changed
tree: d652b0768900cd21874eb9b8b2399b8dda7640a5
  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-support/
  11. recipes-textproc/
  12. COPYING.apache-2.0
  13. COPYING.MIT
  14. LICENSE
  15. MAINTAINERS
  16. README.md
  17. 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.