Some customers if building Torizon OS with Yocto, add their own manifest to help easily manage their custom layers and such. However, the behavior of our setup script causes an easy to miss effect that can have unexpected results on customer builds. This is an excerpt from our Yocto setup script:
if [ -L "$MANIFEST_FILE" ]; then
if [ "$(basename `readlink -f "$MANIFEST_FILE"`)" != "default.xml" ]; then
INTEGRATION_BUILD=1
fi
else
if ! cat $MANIFEST_FILE | grep -q "torizoncore/default.xml"; then
INTEGRATION_BUILD=1
fi
fi
if [ "$INTEGRATION_BUILD" = "1" ] && [ "$AUTO_CONF_CREATED" = "0" ]; then
cat > conf/auto.conf <<EOF
# This is needed when building on integration. With use-head-next you
# always get the newest software (u-boot, kernel, aktualizr-torizon, etc).
# Building on integration without use-head-next your build may fail.
DISTROOVERRIDES .= ":use-head-next"
Basically the script checks if the manifest used for this build is default.xml or not. If not it sets use-head-next in the build. This causes the latest commit for various recipes to be fetched instead of the pinned commit. This can be surprising and unexpected behavior for users if they do not know about this interaction. As it would cause their builds to appear to be unstable or not-reproducible.
Some customers if building Torizon OS with Yocto, add their own manifest to help easily manage their custom layers and such. However, the behavior of our setup script causes an easy to miss effect that can have unexpected results on customer builds. This is an excerpt from our Yocto setup script:
Basically the script checks if the manifest used for this build is default.xml or not. If not it sets use-head-next in the build. This causes the latest commit for various recipes to be fetched instead of the pinned commit. This can be surprising and unexpected behavior for users if they do not know about this interaction. As it would cause their builds to appear to be unstable or not-reproducible.
Community post for reference: https://community.toradex.com/t/imx8mp-u-boot-toradex-recipe-for-torizon-core-docker-not-stable-reproducible/24172