From 272f2083d46a5a023d0d18dcd3e8540a7c5c1cc8 Mon Sep 17 00:00:00 2001 From: Ross Burton Date: Fri, 25 Feb 2022 11:06:27 +0000 Subject: layer.conf: change layer priority to match oe-core Layer priority is the ultimate decider of what recipe is used: if layer A has recipe foo_1 and layer B has recipe foo_2, if layer A's priority is higher than B then foo_1 will be used, even though the version in B is higher, and even if PREFERRED_VERSION_foo is set to 2. This complicates recipes moving between layers, for example when a newer version of a recipe (say, python3-wheel) is taken from a layer with a higher priority (say, meta-python) and moved to a layer with a lower priority (say, oe-core) then it has to be removed before it is added: there is no way to have it in both layers and work correctly. Higher priorities are useful in distribution layers where you may want to override specific recipes without any other fuss. However as all of the layers in meta-oe simply add more recipes in defined areas, there's no need to have a higher layer priority. Signed-off-by: Ross Burton Signed-off-by: Khem Raj --- meta-webserver/conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'meta-webserver/conf') diff --git a/meta-webserver/conf/layer.conf b/meta-webserver/conf/layer.conf index 312c39b3b3..5ae5e796ae 100644 --- a/meta-webserver/conf/layer.conf +++ b/meta-webserver/conf/layer.conf @@ -9,7 +9,7 @@ BBFILES += "${LAYERDIR}/recipes-*/*/*.bb ${LAYERDIR}/recipes-*/*/*.bbappend" BBFILE_COLLECTIONS += "webserver" BBFILE_PATTERN_webserver := "^${LAYERDIR}/" -BBFILE_PRIORITY_webserver = "6" +BBFILE_PRIORITY_webserver = "5" # This should only be incremented on significant changes that will # cause compatibility issues with other layers -- cgit 1.2.3-korg