TorizonCore meta-layers & firewalls

Two of the Toradex-supplied meta-layers have recipes that explicitly specify gitsm:// URLs with no protocol or with explicit protocol=git in the fetch. This is likely to break if the build is done behind a corporate firewall. Replacing this with protocol=https is much more firewall-friendly and has no observable effect on the build process.

Some of the below are not managed by Torazon.

meta-openembedded
M       meta-oe/recipes-extended/ostree/ostree_2020.3.bb
meta-toradex-bsp-common
M       recipes-kernel/backports/backports_5.4.bb
meta-toradex-nxp
M       recipes-kernel/linux/linux-toradex_5.4-2.1.x.bb
meta-updater
M       recipes-sota/aktualizr/aktualizr_git.bb

A typical patch is

diff --git a/recipes-kernel/linux/linux-toradex_5.4-2.1.x.bb b/recipes-kernel/linux/linux-toradex_5.4-2.1.x.bb
index 58c85b5..c6770aa 100644
--- a/recipes-kernel/linux/linux-toradex_5.4-2.1.x.bb
+++ b/recipes-kernel/linux/linux-toradex_5.4-2.1.x.bb
@@ -16,3 +16,3 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=bbea815ee2795b2f4230826c0c6b8814"
 SRC_URI = " \
-    git://git.toradex.com/linux-toradex.git;protocol=git;branch=${SRCBRANCH} \
+    git://git.toradex.com/linux-toradex.git;protocol=https;branch=${SRCBRANCH} \
     file://defconfig \

Greetings @gregb,

Thank you for your continued feedback. I’ll bring this up with the team that manages our layers and see if this small change is possible from our side by default. As you said it would be a nicer experience for those in a situation similar to yours.

Best Regards,
Jeremias