gbmcweb: Allow multiple cloning from multiple repositories

If a single platform has plugins spread across multiple layers, each
layer would be responsible for appending their repo URL to SRC_URI.
This requires each URL to have its own name tag to support multiple
SRCREV targets.

Specify a name for the default plugin repository and have it clone at
the top level of the source directory. This does not change the
behaviour of the recipe when cloning from only a single URI.

Google-Bug-Id: 305022968
Change-Id: Ic244338863095fe3bd60222244789cdc4ebb43a0
Signed-off-by: Vlad Sytchenko <vsytch@google.com>
1 file changed
tree: 97f2b7f7c1ee542cdf293b8a0b32ae1a8c2fff8c
  1. conf/
  2. dynamic-layers/
  3. recipes-bsp/
  4. recipes-connectivity/
  5. recipes-core/
  6. recipes-devtools/
  7. recipes-extended/
  8. recipes-google/
  9. recipes-kernel/
  10. recipes-phosphor/
  11. recipes-support/
  12. LICENSE
  13. README.md
README.md

meta-gbmc-staging

This repository contains additions to the openbmc/meta-google layer that are not yet ready for OpenBMC inclusion.

How to use this layer

  1. Clone openbmc/openbmc from GitHub.
  2. Clone this layer from GitHub into a subdirectory of openbmc.