PACKAGECONFIG definition for a feature such as qt5/6 support doesn't
have to be in an external .bbappend, as in itself it doesn't change
how a recipe is being built, it only defines a recipe option,
component command line switches to enable it, and dependencies that
need to be fulfilled.
If there
I noticed that there are some recipes in OE-core that depend on
recipes living in third-party layers which are not in LAYERDEPENDS.
For instance: gstreamer1.0-plugins-good has a PACKAGECONFIG switch for
qt5 which pulls in a bunch of packages from meta-qt5 but the core
layer (obviously) doesn't
