| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
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
|
|
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I588025b614416c43aa2d053765ab53bacf890cb5
|
|
Add additional providers with whitelists to distro or machine
configuration and not in recipe context (bbappend) otherwise ipmid will
not know about whitelists.
(From meta-phosphor rev: 997610111f30b51742478258aa9b5513f10901e9)
Change-Id: I652935f62485371f5abb517832cbf2284db8e08b
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
Signed-off-by: Andrew Geissler <geissonator@yahoo.com>
|
|
This class is on its way to being deprecated, and oe-core packagegroups
don't have a LICENSE specified in the recipe. Adopt the same semantics
for meta-phosphor.
(From meta-phosphor rev: 72c0635ff972e51d502c43ae7de6e775a6bb5aa0)
Change-Id: I601ae5c5618cd098459baebbd5109972b52385e7
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
|
Adopt a more conventional directory hierarchy. meta-phosphor is still
a _long_ way from suitable for hosting on yoctoproject.org but things
like this don't help.
(From meta-phosphor rev: 471cfcefa74b8c7ceb704cb670e6d915cf27c63b)
Change-Id: I3f106b2f6cdc6cec734be28a6090800546f362eb
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
|
