summaryrefslogtreecommitdiff
path: root/meta-phosphor/recipes-phosphor/packagegroups/packagegroup-obmc-yaml-providers.bb
AgeCommit message (Collapse)AuthorFilesLines
2022-09-20Run oe-stylize on our filesEd Tanous1-8/+7
In all of our recipes, we should be following yoctos lead on formatting, order, and other things, for consistency in our meta layers. This commit runs oe-stylize.py on all of our files. The types of changes being made can be seen in the commit, but amount to: 1. Setting an explicit key ordering 2. Sectioning the files appropriately 3. Applying rules checking to our files At some point in the near future, we would turn this on as part of repotest, but some minor changes need to be upstreamed to meta-oe (WIP) to make that happen. Looking for input on whether this is something we'd like to do, and whether the diffs below look reasonable to folks. Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I489dd21d38a9fe4f3ece89cc7a5e1d0463224abf
2021-08-11meta-phosphor: prep for new override syntaxPatrick Williams1-1/+1
Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
2020-06-16meta-phosphor: define packagegroup for target YAML providersPatrick Williams1-0/+19
As part of the transition away from packages with dual native/target variants where the native variant supplies YAML, add a packagegroup to contain all of the YAML-only packages. (From meta-phosphor rev: 9c39fb1e0cd3de5df55bfaa10e8daba591ff402b) Signed-off-by: Patrick Williams <patrick@stwcx.xyz> Change-Id: I8c7e09f040e90d599903c1923effbf51c259dab6 Signed-off-by: Andrew Geissler <geissonator@yahoo.com>