openbmc/docs/meta-layer-guidelines.md

10 ## Meta layers should not patch projects that exist within the openBMC tree
21 in code review. If patches are checked into meta layers, generally the
28 feature you're building needs to be configurable, or if it can be applied to all
31 If it needs to be per-project or per-machine configurable, check it in under a
35 ## Meta layers should not patch Yocto recipes and projects
49 cherry-pick the commit into the OpenBMC tree, with a pointer to the review in
55 ## Meta layers should avoid using EXTRA_OEMAKE and EXTRA_OEMESON
66 autotools to meson, in pursuit of other goals. Having tool-specific
74 ## Meta layers should not have recipes that point to proprietary licensed code
109 ## Meta layers should not point to OpenBMC specific repositories outside of
118 - Relies on or implements on OpenBMC defined Dbus interfaces.
119 - Is not designed with configurability to be used outside of OpenBMC
120 - Relies on OpenBMC specific layouts, configuration information to accomplish
127 Keeping all long-term-supported code in the OpenBMC github ensures that the
129 OpenBMC-specific code outside of github limits the ability of the project to do