all: http to https everything
PATCH 1/1 all: http to https everything
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
--- meta-ti-bsp/recipes-bsp/cmem/cmem.inc | 2 +- meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc | 2 +- meta-ti-extras/recipes-ti/bios/ti-sysbios.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc | 2 +- meta-ti-extras/recipes-ti/dsplib/dsplib.inc | 2 +- .../framework-components/ti-framework-components.inc | 4 ++-- meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc | 2 +- meta-ti-extras/recipes-ti/mathlib/mathlib.inc | 2 +- meta-ti-extras/recipes-ti/osal/ti-osal.inc | 4 ++-- meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/xdais/ti-xdais.inc | 4 ++-- 15 files changed, 22 insertions(+), 22 deletions(-)
meta-ti-bsp/recipes-bsp/cmem/cmem.inc +1 -1
@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:CMEM" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:CMEM" LICENSE = "GPL-2.0-only" LIC_FILES_CHKSUM = "file://include/ti/cmem.h;beginline=1;endline=30;md5=26be509e4bb413905bda8309e338e2b1"
meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc +1 -1
@@ -1,5 +1,5 @@ DESCRIPTION = "TI Inter Process Communication (IPC) Mechanisms (for Uni- and Multi- Processor Configurations)" -HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE="https://processors.wiki.ti.com/index.php/Category:IPC" LICENSE = "BSD-3-Clause" LIC_FILES_CHKSUM = "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9b710fd7c95e545b91cec79255"
meta-ti-extras/recipes-ti/bios/ti-sysbios.inc +2 -2
@@ -1,5 +1,5 @@ DESCRIPTION = "TI SYS/BIOS v6 Kernel" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" SECTION = "devel" LICENSE = "BSD-3-Clause"
@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/bios_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" BINFILE="bios_${PV}.bin" TI_BIN_UNPK_CMDS="Y: q:workdir:Y"
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1 -1
@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" BINFILE="ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin" TI_BIN_UNPK_CMDS="Y:qY:workdir: : "
meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc +2 -2
@@ -1,5 +1,5 @@ -DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - http://rtsc.eclipse.org)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" +DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - https://rtsc.eclipse.org)" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" SECTION = "devel" LICENSE = "BSD-3-Clause & GPL-2.0-only"
meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc +1 -1
@@ -2,4 +2,4 @@ require ti-xdctools-common.inc S = "${WORKDIR}/xdctools_${PV}_core" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip"
meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc +1 -1
@@ -3,7 +3,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/xdctools_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" BINFILE="xdctools_setuplinux_${PV}.bin" TI_BIN_UNPK_CMDS="Y:workdir:Y"
meta-ti-extras/recipes-ti/dsplib/dsplib.inc +1 -1
@@ -1,5 +1,5 @@ SUMMARY = "DSPLIB contains optimized signal processing functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/dsplib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/dsplib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.inc
meta-ti-extras/recipes-ti/framework-components/ti-framework-components.inc +2 -2
@@ -1,5 +1,5 @@ DESCRIPTION = "TI Framework Components" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" SECTION = "devel" LICENSE = "BSD-3-Clause"
@@ -7,7 +7,7 @@ require recipes-ti/includes/ti-paths.inc S = "${WORKDIR}/framework_components_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc +2 -2
@@ -1,5 +1,5 @@ DESCRIPTION = "IMGLIB contains optimized general-purpose image/video processing routines for TI DSPs" -HOMEPAGE = "http://www.ti.com/tool/sprc264" +HOMEPAGE = "https://www.ti.com/tool/sprc264" SECTION = "devel" LICENSE = "BSD-3-Clause"
@@ -9,7 +9,7 @@ require ../includes/ti-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" +SRC_URI = "https://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" S = "${WORKDIR}/imglib-c66x-${PV}"
meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc +1 -1
@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:IPC" require recipes-ti/ipc/ti-ipc-common.inc require ti-ipc-rtos.inc
meta-ti-extras/recipes-ti/mathlib/mathlib.inc +1 -1
@@ -1,5 +1,5 @@ SUMMARY = "MATHLIB contains optimized floating-point math functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/mathlib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/mathlib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.inc
meta-ti-extras/recipes-ti/osal/ti-osal.inc +2 -2
@@ -1,5 +1,5 @@ DESCRIPTION = "TI Operating System Abstraction Library (OSAL)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" LICENSE = "BSD-3-Clause & EPL-1.0" SECTION = "devel"
@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/osal_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" do_install() { install -d ${D}${OSAL_INSTALL_DIR_RECIPE}
meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc +2 -2
@@ -1,5 +1,5 @@ DESCRIPTION = "TI Vision Library (VLIB) for C66x" -HOMEPAGE = "http://software-dl.ti.com/libs/vlib/latest/index_FDS.html" +HOMEPAGE = "https://software-dl.ti.com/libs/vlib/latest/index_FDS.html" SECTION = "devel" LICENSE = "TI-TSPA & BSD-3-Clause"
@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" +SRC_URI = "https://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" S = "${WORKDIR}/vlib_c66x_${PV}"
meta-ti-extras/recipes-ti/xdais/ti-xdais.inc +2 -2
@@ -1,5 +1,5 @@ DESCRIPTION = "TI eXpress DSP Algorithm Interface Standard (XDAIS) specification" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" LICENSE = "GPL-2.0-only" SECTION = "devel"
@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/xdais_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
Signature · 1 line
2.40.0
Quoted 70 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>--- meta-ti-bsp/recipes-bsp/cmem/cmem.inc | 2 +- meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc | 2 +- meta-ti-extras/recipes-ti/bios/ti-sysbios.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc | 2 +- meta-ti-extras/recipes-ti/dsplib/dsplib.inc | 2 +- .../framework-components/ti-framework-components.inc | 4 ++-- meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc | 2 +- meta-ti-extras/recipes-ti/mathlib/mathlib.inc | 2 +- meta-ti-extras/recipes-ti/osal/ti-osal.inc | 4 ++-- meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/xdais/ti-xdais.inc | 4 ++-- 15 files changed, 22 insertions(+), 22 deletions(-)meta-ti-bsp/recipes-bsp/cmem/cmem.inc +1
-1@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:CMEM" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:CMEM" LICENSE = "GPL-2.0-only" LIC_FILES_CHKSUM = "file://include/ti/cmem.h;beginline=1;endline=30;md5=26be509e4bb413905bda8309e338e2b1"meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc +1
-1@@ -1,5 +1,5 @@ DESCRIPTION = "TI Inter Process Communication (IPC) Mechanisms (for Uni- and Multi- Processor Configurations)" -HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE="https://processors.wiki.ti.com/index.php/Category:IPC" LICENSE = "BSD-3-Clause" LIC_FILES_CHKSUM = "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9b710fd7c95e545b91cec79255"meta-ti-extras/recipes-ti/bios/ti-sysbios.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI SYS/BIOS v6 Kernel" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/bios_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" BINFILE="bios_${PV}.bin" TI_BIN_UNPK_CMDS="Y: q:workdir:Y"meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 14
Quoted 5 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"
Don't actually merge this. Wanted to take this opportunity to ask what on earth theses SRC_URIs are. What do these mean, what's the story?
Quoted 170 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0BINFILE="ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin" TI_BIN_UNPK_CMDS="Y:qY:workdir: : "meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc +2
-2@@ -1,5 +1,5 @@ -DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - http://rtsc.eclipse.org)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" +DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - https://rtsc.eclipse.org)" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" SECTION = "devel" LICENSE = "BSD-3-Clause & GPL-2.0-only"meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc +1
-1@@ -2,4 +2,4 @@ require ti-xdctools-common.inc S = "${WORKDIR}/xdctools_${PV}_core" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip"meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc +1
-1@@ -3,7 +3,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/xdctools_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" BINFILE="xdctools_setuplinux_${PV}.bin" TI_BIN_UNPK_CMDS="Y:workdir:Y"meta-ti-extras/recipes-ti/dsplib/dsplib.inc +1
-1@@ -1,5 +1,5 @@ SUMMARY = "DSPLIB contains optimized signal processing functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/dsplib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/dsplib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.incmeta-ti-extras/recipes-ti/framework-components/ti-framework-components.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Framework Components" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -7,7 +7,7 @@ require recipes-ti/includes/ti-paths.inc S = "${WORKDIR}/framework_components_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "IMGLIB contains optimized general-purpose image/video processing routines for TI DSPs" -HOMEPAGE = "http://www.ti.com/tool/sprc264" +HOMEPAGE = "https://www.ti.com/tool/sprc264" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" +SRC_URI = "https://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" S = "${WORKDIR}/imglib-c66x-${PV}"meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc +1
-1@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:IPC" require recipes-ti/ipc/ti-ipc-common.inc require ti-ipc-rtos.incmeta-ti-extras/recipes-ti/mathlib/mathlib.inc +1
-1@@ -1,5 +1,5 @@ SUMMARY = "MATHLIB contains optimized floating-point math functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/mathlib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/mathlib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.incmeta-ti-extras/recipes-ti/osal/ti-osal.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Operating System Abstraction Library (OSAL)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" LICENSE = "BSD-3-Clause & EPL-1.0" SECTION = "devel"@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/osal_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" do_install() { install -d ${D}${OSAL_INSTALL_DIR_RECIPE}meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Vision Library (VLIB) for C66x" -HOMEPAGE = "http://software-dl.ti.com/libs/vlib/latest/index_FDS.html" +HOMEPAGE = "https://software-dl.ti.com/libs/vlib/latest/index_FDS.html" SECTION = "devel" LICENSE = "TI-TSPA & BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" +SRC_URI = "https://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" S = "${WORKDIR}/vlib_c66x_${PV}"meta-ti-extras/recipes-ti/xdais/ti-xdais.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI eXpress DSP Algorithm Interface Standard (XDAIS) specification" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" LICENSE = "GPL-2.0-only" SECTION = "devel"@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/xdais_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
Quoted 64 lines · Randolph Sapp
Quoted 63 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>--- meta-ti-bsp/recipes-bsp/cmem/cmem.inc | 2 +- meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc | 2 +- meta-ti-extras/recipes-ti/bios/ti-sysbios.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc | 2 +- meta-ti-extras/recipes-ti/dsplib/dsplib.inc | 2 +- .../framework-components/ti-framework-components.inc | 4 ++-- meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc | 2 +- meta-ti-extras/recipes-ti/mathlib/mathlib.inc | 2 +- meta-ti-extras/recipes-ti/osal/ti-osal.inc | 4 ++-- meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/xdais/ti-xdais.inc | 4 ++-- 15 files changed, 22 insertions(+), 22 deletions(-)meta-ti-bsp/recipes-bsp/cmem/cmem.inc +1
-1@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:CMEM" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:CMEM" LICENSE = "GPL-2.0-only" LIC_FILES_CHKSUM = "file://include/ti/cmem.h;beginline=1;endline=30;md5=26be509e4bb413905bda8309e338e2b1"meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc +1
-1@@ -1,5 +1,5 @@ DESCRIPTION = "TI Inter Process Communication (IPC) Mechanisms (for Uni- and Multi- Processor Configurations)" -HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE="https://processors.wiki.ti.com/index.php/Category:IPC" LICENSE = "BSD-3-Clause" LIC_FILES_CHKSUM = "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9b710fd7c95e545b91cec79255"meta-ti-extras/recipes-ti/bios/ti-sysbios.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI SYS/BIOS v6 Kernel" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/bios_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" BINFILE="bios_${PV}.bin" TI_BIN_UNPK_CMDS="Y: q:workdir:Y"meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0
Quoted 8 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 12
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"Don't actually merge this. Wanted to take this opportunity to ask what on earth theses
SRC_URIsare. What do these mean, what's the story?
Heh, these were placeholders for "clickwrap" packages, which at some point long time ago TI Legal considered a "great" way to distribute software... Basically, there was no direct download URL - you must have downloaded them manually by filling out an online form and signing some sort of an agreement, which would trigger the download. Then you "install the source into the local downloads dir" (hence the name) by copying what you've downloaded manually into your ${DL_DIR} and Bitbake would be able to find it there regardless of the actual SRC_URI.
Quoted 138 lines
Quoted 138 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0BINFILE="ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin" TI_BIN_UNPK_CMDS="Y:qY:workdir: : "meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc +2
-2@@ -1,5 +1,5 @@ -DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - http://rtsc.eclipse.org)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" +DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - https://rtsc.eclipse.org)" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" SECTION = "devel" LICENSE = "BSD-3-Clause & GPL-2.0-only"meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc +1
-1@@ -2,4 +2,4 @@ require ti-xdctools-common.inc S = "${WORKDIR}/xdctools_${PV}_core" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip"meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc +1
-1@@ -3,7 +3,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/xdctools_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" BINFILE="xdctools_setuplinux_${PV}.bin" TI_BIN_UNPK_CMDS="Y:workdir:Y"meta-ti-extras/recipes-ti/dsplib/dsplib.inc +1
-1@@ -1,5 +1,5 @@ SUMMARY = "DSPLIB contains optimized signal processing functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/dsplib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/dsplib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.incmeta-ti-extras/recipes-ti/framework-components/ti-framework-components.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Framework Components" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -7,7 +7,7 @@ require recipes-ti/includes/ti-paths.inc S = "${WORKDIR}/framework_components_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "IMGLIB contains optimized general-purpose image/video processing routines for TI DSPs" -HOMEPAGE = "http://www.ti.com/tool/sprc264" +HOMEPAGE = "https://www.ti.com/tool/sprc264" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" +SRC_URI = "https://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" S = "${WORKDIR}/imglib-c66x-${PV}"meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc +1
-1@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:IPC" require recipes-ti/ipc/ti-ipc-common.inc require ti-ipc-rtos.incmeta-ti-extras/recipes-ti/mathlib/mathlib.inc +1
-1@@ -1,5 +1,5 @@ SUMMARY = "MATHLIB contains optimized floating-point math functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/mathlib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/mathlib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.incmeta-ti-extras/recipes-ti/osal/ti-osal.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Operating System Abstraction Library (OSAL)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" LICENSE = "BSD-3-Clause & EPL-1.0" SECTION = "devel"@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/osal_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" do_install() { install -d ${D}${OSAL_INSTALL_DIR_RECIPE}meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Vision Library (VLIB) for C66x" -HOMEPAGE = "http://software-dl.ti.com/libs/vlib/latest/index_FDS.html" +HOMEPAGE = "https://software-dl.ti.com/libs/vlib/latest/index_FDS.html" SECTION = "devel" LICENSE = "TI-TSPA & BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" +SRC_URI = "https://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" S = "${WORKDIR}/vlib_c66x_${PV}"meta-ti-extras/recipes-ti/xdais/ti-xdais.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI eXpress DSP Algorithm Interface Standard (XDAIS) specification" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" LICENSE = "GPL-2.0-only" SECTION = "devel"@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/xdais_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
Quoted 74 lines · Denys Dmytriyenko
Quoted 64 lines · Randolph Sapp
Quoted 63 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>--- meta-ti-bsp/recipes-bsp/cmem/cmem.inc | 2 +- meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc | 2 +- meta-ti-extras/recipes-ti/bios/ti-sysbios.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc | 4 ++-- meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc | 2 +- meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc | 2 +- meta-ti-extras/recipes-ti/dsplib/dsplib.inc | 2 +- .../framework-components/ti-framework-components.inc | 4 ++-- meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc | 2 +- meta-ti-extras/recipes-ti/mathlib/mathlib.inc | 2 +- meta-ti-extras/recipes-ti/osal/ti-osal.inc | 4 ++-- meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc | 4 ++-- meta-ti-extras/recipes-ti/xdais/ti-xdais.inc | 4 ++-- 15 files changed, 22 insertions(+), 22 deletions(-)meta-ti-bsp/recipes-bsp/cmem/cmem.inc +1
-1@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:CMEM" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:CMEM" LICENSE = "GPL-2.0-only" LIC_FILES_CHKSUM = "file://include/ti/cmem.h;beginline=1;endline=30;md5=26be509e4bb413905bda8309e338e2b1"meta-ti-bsp/recipes-ti/ipc/ti-ipc.inc +1
-1@@ -1,5 +1,5 @@ DESCRIPTION = "TI Inter Process Communication (IPC) Mechanisms (for Uni- and Multi- Processor Configurations)" -HOMEPAGE="http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE="https://processors.wiki.ti.com/index.php/Category:IPC" LICENSE = "BSD-3-Clause" LIC_FILES_CHKSUM = "file://${S}/ipc-linux.mak;beginline=1;endline=30;md5=7b327f9b710fd7c95e545b91cec79255"meta-ti-extras/recipes-ti/bios/ti-sysbios.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI SYS/BIOS v6 Kernel" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/bios_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/bios/sysbios/${PV}/exports/bios_setuplinux_${PV}.bin;name=sysbiosbin" BINFILE="bios_${PV}.bin" TI_BIN_UNPK_CMDS="Y: q:workdir:Y"meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0Quoted 8 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 12
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"Don't actually merge this. Wanted to take this opportunity to ask what on earth theses
SRC_URIsare. What do these mean, what's the story?
Quoted 9 lines
Heh, these were placeholders for "clickwrap" packages, which at some point long time ago TI Legal considered a "great" way to distribute software... Basically, there was no direct download URL - you must have downloaded them manually by filling out an online form and signing some sort of an agreement, which would trigger the download. Then you "install the source into the local downloads dir" (hence the name) by copying what you've downloaded manually into your ${DL_DIR} and Bitbake would be able to find it there regardless of the actual
SRC_URI.
Oh cool, I hate it. (Thanks for the explanation, I just really don't like this idea.) Can we drop these (install methods or packages if necessary) or will policy not allow it? Also, is this URI functionality baked into the http fetcher or is this just leaning on bitbake being unable to resolve the domain and then falling back on the local copy?
Quoted 139 lines
Quoted 139 lines
Quoted 139 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0BINFILE="ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin" TI_BIN_UNPK_CMDS="Y:qY:workdir: : "meta-ti-extras/recipes-ti/devtools/ti-xdctools-common.inc +2
-2@@ -1,5 +1,5 @@ -DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - http://rtsc.eclipse.org)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" +DESCRIPTION = "TI XDCtools (RTSC - Real Time Software Components - https://rtsc.eclipse.org)" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc" SECTION = "devel" LICENSE = "BSD-3-Clause & GPL-2.0-only"meta-ti-extras/recipes-ti/devtools/ti-xdctools-core.inc +1
-1@@ -2,4 +2,4 @@ require ti-xdctools-common.inc S = "${WORKDIR}/xdctools_${PV}_core" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdccore/xdctools_${PV}_core_linux.zip;name=xdczip"meta-ti-extras/recipes-ti/devtools/ti-xdctools.inc +1
-1@@ -3,7 +3,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/xdctools_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/rtsc/${PV}/exports/xdctools_setuplinux_${PV}.bin;name=xdcbin" BINFILE="xdctools_setuplinux_${PV}.bin" TI_BIN_UNPK_CMDS="Y:workdir:Y"meta-ti-extras/recipes-ti/dsplib/dsplib.inc +1
-1@@ -1,5 +1,5 @@ SUMMARY = "DSPLIB contains optimized signal processing functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/dsplib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/dsplib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.incmeta-ti-extras/recipes-ti/framework-components/ti-framework-components.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Framework Components" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -7,7 +7,7 @@ require recipes-ti/includes/ti-paths.inc S = "${WORKDIR}/framework_components_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/fc/${PV}/exports/framework_components_${PV},lite.tar.gz;name=fctarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"meta-ti-extras/recipes-ti/imglib/imglib-c66x.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "IMGLIB contains optimized general-purpose image/video processing routines for TI DSPs" -HOMEPAGE = "http://www.ti.com/tool/sprc264" +HOMEPAGE = "https://www.ti.com/tool/sprc264" SECTION = "devel" LICENSE = "BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" +SRC_URI = "https://software-dl.ti.com/sdoemb/sdoemb_public_sw/imglib/${PV}/exports/${BINFILE};name=imglib" S = "${WORKDIR}/imglib-c66x-${PV}"meta-ti-extras/recipes-ti/ipc/ti-ipc-examples.inc +1
-1@@ -1,4 +1,4 @@ -HOMEPAGE = "http://processors.wiki.ti.com/index.php/Category:IPC" +HOMEPAGE = "https://processors.wiki.ti.com/index.php/Category:IPC" require recipes-ti/ipc/ti-ipc-common.inc require ti-ipc-rtos.incmeta-ti-extras/recipes-ti/mathlib/mathlib.inc +1
-1@@ -1,5 +1,5 @@ SUMMARY = "MATHLIB contains optimized floating-point math functions for TI DSPs" -HOMEPAGE = "http://git.ti.com/ep-processor-libraries/mathlib" +HOMEPAGE = "https://git.ti.com/ep-processor-libraries/mathlib" LICENSE = "BSD-3-Clause" require ../includes/ti-paths.incmeta-ti-extras/recipes-ti/osal/ti-osal.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Operating System Abstraction Library (OSAL)" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal" LICENSE = "BSD-3-Clause & EPL-1.0" SECTION = "devel"@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/osal_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/osal/${PV}/exports/osal_${PV}.tar.gz;name=osaltarball" do_install() { install -d ${D}${OSAL_INSTALL_DIR_RECIPE}meta-ti-extras/recipes-ti/vlib/vlib-c66x.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI Vision Library (VLIB) for C66x" -HOMEPAGE = "http://software-dl.ti.com/libs/vlib/latest/index_FDS.html" +HOMEPAGE = "https://software-dl.ti.com/libs/vlib/latest/index_FDS.html" SECTION = "devel" LICENSE = "TI-TSPA & BSD-3-Clause"@@ -9,7 +9,7 @@ require ../includes/ti-eula-unpack.inc COMPATIBLE_MACHINE = "omap-a15" -SRC_URI = "http://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" +SRC_URI = "https://software-dl.ti.com/libs/vlib/${PV}//exports/vlib_c66x_obj_${PV}_Linux.bin;name=vlibbin" S = "${WORKDIR}/vlib_c66x_${PV}"meta-ti-extras/recipes-ti/xdais/ti-xdais.inc +2
-2@@ -1,5 +1,5 @@ DESCRIPTION = "TI eXpress DSP Algorithm Interface Standard (XDAIS) specification" -HOMEPAGE = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" +HOMEPAGE = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais" LICENSE = "GPL-2.0-only" SECTION = "devel"@@ -8,7 +8,7 @@ require ../includes/ti-staging.inc S = "${WORKDIR}/xdais_${PV}" -SRC_URI = "http://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" +SRC_URI = "https://software-dl.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/xdais/${PV}/exports/xdais_${PV}.tar.gz;name=xdaistarball" do_install() { CP_ARGS="-Prf --preserve=mode,timestamps --no-preserve=ownership"
Quoted 10 lines · Randolph Sapp
Quoted 9 lines · Denys Dmytriyenko
Quoted 8 lines · Randolph Sapp
Quoted 7 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>---
<snip>
Quoted 23 lines
Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0Quoted 8 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 12
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"Don't actually merge this. Wanted to take this opportunity to ask what on earth theses
SRC_URIsare. What do these mean, what's the story?Quoted 9 lines
Heh, these were placeholders for "clickwrap" packages, which at some point long time ago TI Legal considered a "great" way to distribute software... Basically, there was no direct download URL - you must have downloaded them manually by filling out an online form and signing some sort of an agreement, which would trigger the download. Then you "install the source into the local downloads dir" (hence the name) by copying what you've downloaded manually into your ${DL_DIR} and Bitbake would be able to find it there regardless of the actual
SRC_URI.
Quoted 3 lines
Oh cool, I hate it. (Thanks for the explanation, I just really don't like this idea.) Can we drop these (install methods or packages if necessary) or will policy not allow it?
Nobody likes it on the engineering side! :) But it was forced back in the day by sales/marketing/legal and took a lot of effort to convince everyone that this clickwrap stuff doesn't bring much benefit, but causes damage...
Since then most if not all of TI packages dropped clickwrap and allowed direct download. Hence you don't see a lot of these weird URLs in recipes any more.
Not sure about CodeGen Tool for TMS470 MCU and if there were newer releases or if it's still active - nobody cared to update this recipe in over 10 years. Other CGT recipes for ARM, PRU, C6x, C7x etc. in that recipes-ti/devtools directory were kept mostly up to date, but not for TMS470. Not sure if there are any downstream users anymore, maybe time to remove it...
Quoted 4 lines
Also, is this URI
functionality baked into the http fetcher or is this just leaning on bitbake being unable to resolve the domain and then falling back on the local copy?
This is basic Bitbake fetcher functionality and is well documented. High level order of operations to locate sources:
1. Check if you already have them in your local DL_DIR
2. Go through the list of configured PREMIRRORS to locate the sources there
3. Actually hit the upstream SRC_URI and try to download the original src
4. If everything else fails, check through the list of "post" MIRRORS
So, requiring user to pre-download the sources manually and placing them in their local DL_DIR per the original documentation would shortcut the process at step 1.
Otherwise it would break at step 3 (and 4) and hopefully the weird URL would give user some clues or at least force to read the docs...
There's nothing special about the URL, besides the convention that .local is reserved - https://en.wikipedia.org/wiki/.local - and the entire name suggesting to install the sources in local dir :)
Signature · 1 line
Denys
Quoted 46 lines · Denys Dmytriyenko
Quoted 10 lines · Randolph Sapp
Quoted 9 lines · Denys Dmytriyenko
Quoted 8 lines · Randolph Sapp
Quoted 7 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>---
<snip>
Quoted 23 lines
Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0Quoted 8 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 12
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"Don't actually merge this. Wanted to take this opportunity to ask what on earth theses
SRC_URIsare. What do these mean, what's the story?Quoted 9 lines
Heh, these were placeholders for "clickwrap" packages, which at some point long time ago TI Legal considered a "great" way to distribute software... Basically, there was no direct download URL - you must have downloaded them manually by filling out an online form and signing some sort of an agreement, which would trigger the download. Then you "install the source into the local downloads dir" (hence the name) by copying what you've downloaded manually into your ${DL_DIR} and Bitbake would be able to find it there regardless of the actual
SRC_URI.Quoted 3 lines
Oh cool, I hate it. (Thanks for the explanation, I just really don't like this idea.) Can we drop these (install methods or packages if necessary) or will policy not allow it?
Nobody likes it on the engineering side! :) But it was forced back in the day by sales/marketing/legal and took a lot of effort to convince everyone that this clickwrap stuff doesn't bring much benefit, but causes damage...
Quoted 9 lines
Since then most if not all of TI packages dropped clickwrap and allowed direct download. Hence you don't see a lot of these weird URLs in recipes any more.
Not sure about CodeGen Tool for TMS470 MCU and if there were newer releases or if it's still active - nobody cared to update this recipe in over 10 years. Other CGT recipes for ARM, PRU, C6x, C7x etc. in that recipes-ti/devtools directory were kept mostly up to date, but not for TMS470. Not sure if there are any downstream users anymore, maybe time to remove it...
I'll add a patch to drop codegen then. It'll be a little bit of a scream test but I'm sure it's fine. The C7 / C6 components I know still have a few dependents in meta-arago though, so I don't think those can be dropped. Will see if there is a non-clickwrapped source for those yet.
Quoted 18 lines
Quoted 5 lines
Also, is this URI
functionality baked into the http fetcher or is this just leaning on bitbake being unable to resolve the domain and then falling back on the local copy?This is basic Bitbake fetcher functionality and is well documented. High level order of operations to locate sources:
1. Check if you already have them in your local
DL_DIR
2. Go through the list of configured PREMIRRORS to locate the sources there
3. Actually hit the upstreamSRC_URIand try to download the original src
4. If everything else fails, check through the list of "post" MIRRORSSo, requiring user to pre-download the sources manually and placing them in their local
DL_DIRper the original documentation would shortcut the process at step 1.
Quoted 7 lines
Otherwise it would break at step 3 (and 4) and hopefully the weird URL would give user some clues or at least force to read the docs...
There's nothing special about the URL, besides the convention that .local is reserved - https://en.wikipedia.org/wiki/.local - and the entire name suggesting to install the sources in local dir :)
Ah, alright. At least this isn't that bad then. I still don't like the idea of being able to reach steps 3&4 in this case as it will check http sources. Local is reserved but it's still not a great idea to allow this fetch to go through, even if *ideally* it should fail to resolve.
Quoted 57 lines · Randolph Sapp
Quoted 46 lines · Denys Dmytriyenko
Quoted 10 lines · Randolph Sapp
Quoted 9 lines · Denys Dmytriyenko
Quoted 8 lines · Randolph Sapp
Quoted 7 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>---
<snip>
Quoted 23 lines
Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0Quoted 8 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 12
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"Don't actually merge this. Wanted to take this opportunity to ask what on earth theses
SRC_URIsare. What do these mean, what's the story?Quoted 9 lines
Heh, these were placeholders for "clickwrap" packages, which at some point long time ago TI Legal considered a "great" way to distribute software... Basically, there was no direct download URL - you must have downloaded them manually by filling out an online form and signing some sort of an agreement, which would trigger the download. Then you "install the source into the local downloads dir" (hence the name) by copying what you've downloaded manually into your ${DL_DIR} and Bitbake would be able to find it there regardless of the actual
SRC_URI.Quoted 3 lines
Oh cool, I hate it. (Thanks for the explanation, I just really don't like this idea.) Can we drop these (install methods or packages if necessary) or will policy not allow it?
Nobody likes it on the engineering side! :) But it was forced back in the day by sales/marketing/legal and took a lot of effort to convince everyone that this clickwrap stuff doesn't bring much benefit, but causes damage...
Quoted 9 lines
Since then most if not all of TI packages dropped clickwrap and allowed direct download. Hence you don't see a lot of these weird URLs in recipes any more.
Not sure about CodeGen Tool for TMS470 MCU and if there were newer releases or if it's still active - nobody cared to update this recipe in over 10 years. Other CGT recipes for ARM, PRU, C6x, C7x etc. in that recipes-ti/devtools directory were kept mostly up to date, but not for TMS470. Not sure if there are any downstream users anymore, maybe time to remove it...
Quoted 5 lines
I'll add a patch to drop codegen then. It'll be a little bit of a scream test but I'm sure it's fine. The C7 / C6 components I know still have a few dependents in meta-arago though, so I don't think those can be dropped. Will see if there is a non-clickwrapped source for those yet.
Ah, there's still an older C6x CGT 7.4.16 that is clickwrapped - at some point there was one component remaining that required it, while everything else got migrated to C6x CGT 8.x, which enabled direct download and we have a recipe for version 8.3.2 already. And the recipe for older 7.x was specifically in its own namespace to allow both of them in the same build, until the last dependency for it goes away.
C7x CGT never was clickwrapped, as the arch is newer than those dark times :)
BTW, assuming that meta-arago is the only consumer of meta-ti components is not very safe. But I think dropping CGT for TMS740 and old CGT 7.x for C6x should be fine and those are the only remaining clickwrapped recipes.
IIRC, TMS740 arch was an old ARM MCU, so generic ARM CGT should probably also work, I guess.
Quoted 25 lines
Quoted 17 lines
Quoted 4 lines
Also, is this URI
functionality baked into the http fetcher or is this just leaning on bitbake being unable to resolve the domain and then falling back on the local copy?This is basic Bitbake fetcher functionality and is well documented. High level order of operations to locate sources:
1. Check if you already have them in your local
DL_DIR
2. Go through the list of configured PREMIRRORS to locate the sources there
3. Actually hit the upstreamSRC_URIand try to download the original src
4. If everything else fails, check through the list of "post" MIRRORSSo, requiring user to pre-download the sources manually and placing them in their local
DL_DIRper the original documentation would shortcut the process at step 1.Quoted 7 lines
Otherwise it would break at step 3 (and 4) and hopefully the weird URL would give user some clues or at least force to read the docs...
There's nothing special about the URL, besides the convention that .local is reserved - https://en.wikipedia.org/wiki/.local - and the entire name suggesting to install the sources in local dir :)
Quoted 5 lines
Ah, alright. At least this isn't that bad then. I still don't like the idea of being able to reach steps 3&4 in this case as it will check http sources. Local is reserved but it's still not a great idea to allow this fetch to go through, even if *ideally* it should fail to resolve.
You can try adding do_fetch[network] = "0" to that recipe...
Signature · 1 line
Denys
Quoted 71 lines · Denys Dmytriyenko
Quoted 57 lines · Randolph Sapp
Quoted 46 lines · Denys Dmytriyenko
Quoted 10 lines · Randolph Sapp
Quoted 9 lines · Denys Dmytriyenko
Quoted 8 lines · Randolph Sapp
Quoted 7 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>---
<snip>
Quoted 23 lines
Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0Quoted 8 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 12
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"Don't actually merge this. Wanted to take this opportunity to ask what on earth theses
SRC_URIsare. What do these mean, what's the story?Quoted 9 lines
Heh, these were placeholders for "clickwrap" packages, which at some point long time ago TI Legal considered a "great" way to distribute software... Basically, there was no direct download URL - you must have downloaded them manually by filling out an online form and signing some sort of an agreement, which would trigger the download. Then you "install the source into the local downloads dir" (hence the name) by copying what you've downloaded manually into your ${DL_DIR} and Bitbake would be able to find it there regardless of the actual
SRC_URI.Quoted 3 lines
Oh cool, I hate it. (Thanks for the explanation, I just really don't like this idea.) Can we drop these (install methods or packages if necessary) or will policy not allow it?
Nobody likes it on the engineering side! :) But it was forced back in the day by sales/marketing/legal and took a lot of effort to convince everyone that this clickwrap stuff doesn't bring much benefit, but causes damage...
Quoted 9 lines
Since then most if not all of TI packages dropped clickwrap and allowed direct download. Hence you don't see a lot of these weird URLs in recipes any more.
Not sure about CodeGen Tool for TMS470 MCU and if there were newer releases or if it's still active - nobody cared to update this recipe in over 10 years. Other CGT recipes for ARM, PRU, C6x, C7x etc. in that recipes-ti/devtools directory were kept mostly up to date, but not for TMS470. Not sure if there are any downstream users anymore, maybe time to remove it...
Quoted 5 lines
I'll add a patch to drop codegen then. It'll be a little bit of a scream test but I'm sure it's fine. The C7 / C6 components I know still have a few dependents in meta-arago though, so I don't think those can be dropped. Will see if there is a non-clickwrapped source for those yet.
Ah, there's still an older C6x CGT 7.4.16 that is clickwrapped - at some point there was one component remaining that required it, while everything else got migrated to C6x CGT 8.x, which enabled direct download and we have a recipe for version 8.3.2 already. And the recipe for older 7.x was specifically in its own namespace to allow both of them in the same build, until the last dependency for it goes away.
Quoted 4 lines
C7x CGT never was clickwrapped, as the arch is newer than those dark times :)
BTW, assuming that meta-arago is the only consumer of meta-ti components is not very safe.
Agreed. We are already toying around with supporting OpenBMC which absolutely does not use arago.
Quoted 40 lines
But I think dropping CGT for TMS740 and old CGT 7.x for C6x should be fine and those are the only remaining clickwrapped recipes.
IIRC, TMS740 arch was an old ARM MCU, so generic ARM CGT should probably also work, I guess.
Quoted 25 lines
Quoted 17 lines
Quoted 4 lines
Also, is this URI
functionality baked into the http fetcher or is this just leaning on bitbake being unable to resolve the domain and then falling back on the local copy?This is basic Bitbake fetcher functionality and is well documented. High level order of operations to locate sources:
1. Check if you already have them in your local
DL_DIR
2. Go through the list of configured PREMIRRORS to locate the sources there
3. Actually hit the upstreamSRC_URIand try to download the original src
4. If everything else fails, check through the list of "post" MIRRORSSo, requiring user to pre-download the sources manually and placing them in their local
DL_DIRper the original documentation would shortcut the process at step 1.Quoted 7 lines
Otherwise it would break at step 3 (and 4) and hopefully the weird URL would give user some clues or at least force to read the docs...
There's nothing special about the URL, besides the convention that .local is reserved - https://en.wikipedia.org/wiki/.local - and the entire name suggesting to install the sources in local dir :)
Quoted 5 lines
Ah, alright. At least this isn't that bad then. I still don't like the idea of being able to reach steps 3&4 in this case as it will check http sources. Local is reserved but it's still not a great idea to allow this fetch to go through, even if *ideally* it should fail to resolve.
You can try adding do_fetch[network] = "0" to that recipe...
Signature · 3 lines
Ryan Eatmon [email protected] ----------------------------------------- Texas Instruments, Inc. - LCPD - MGTS
Quoted 74 lines · Ryan Eatmon
Quoted 71 lines · Denys Dmytriyenko
Quoted 57 lines · Randolph Sapp
Quoted 46 lines · Denys Dmytriyenko
Quoted 10 lines · Randolph Sapp
Quoted 9 lines · Denys Dmytriyenko
Quoted 8 lines · Randolph Sapp
Quoted 7 lines · On 4/27/23 19:28, [email protected] wrote:
From: Randolph Sapp <[email protected]>
All of the software-dl links 302 to https urls anyway. Just jump straight to the secure version.
Signed-off-by Randolph Sapp <[email protected]>---
<snip>
Quoted 23 lines
Quoted 13 lines
Quoted 4 lines
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +0
-0Quoted 8 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc require ../includes/ti-eula-unpack.inc · line 12
Quoted 4 lines
meta-ti-extras/recipes-ti/devtools/ti-cgt470.inc +1
-1@@ -11,7 +11,7 @@ require ../includes/ti-eula-unpack.inc S = "${WORKDIR}/cgt470_${PV}" -SRC_URI = "http://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin" +SRC_URI = "https://install.source.dir.local/ti_cgt_tms470_${PVwithdots}_setup_linux_x86.bin;name=cgt470bin"Don't actually merge this. Wanted to take this opportunity to ask what on earth theses
SRC_URIsare. What do these mean, what's the story?Quoted 9 lines
Heh, these were placeholders for "clickwrap" packages, which at some point long time ago TI Legal considered a "great" way to distribute software... Basically, there was no direct download URL - you must have downloaded them manually by filling out an online form and signing some sort of an agreement, which would trigger the download. Then you "install the source into the local downloads dir" (hence the name) by copying what you've downloaded manually into your ${DL_DIR} and Bitbake would be able to find it there regardless of the actual
SRC_URI.Quoted 3 lines
Oh cool, I hate it. (Thanks for the explanation, I just really don't like this idea.) Can we drop these (install methods or packages if necessary) or will policy not allow it?
Nobody likes it on the engineering side! :) But it was forced back in the day by sales/marketing/legal and took a lot of effort to convince everyone that this clickwrap stuff doesn't bring much benefit, but causes damage...
Quoted 9 lines
Since then most if not all of TI packages dropped clickwrap and allowed direct download. Hence you don't see a lot of these weird URLs in recipes any more.
Not sure about CodeGen Tool for TMS470 MCU and if there were newer releases or if it's still active - nobody cared to update this recipe in over 10 years. Other CGT recipes for ARM, PRU, C6x, C7x etc. in that recipes-ti/devtools directory were kept mostly up to date, but not for TMS470. Not sure if there are any downstream users anymore, maybe time to remove it...
Quoted 5 lines
I'll add a patch to drop codegen then. It'll be a little bit of a scream test but I'm sure it's fine. The C7 / C6 components I know still have a few dependents in meta-arago though, so I don't think those can be dropped. Will see if there is a non-clickwrapped source for those yet.
Ah, there's still an older C6x CGT 7.4.16 that is clickwrapped - at some point there was one component remaining that required it, while everything else got migrated to C6x CGT 8.x, which enabled direct download and we have a recipe for version 8.3.2 already. And the recipe for older 7.x was specifically in its own namespace to allow both of them in the same build, until the last dependency for it goes away.
Quoted 7 lines
Quoted 4 lines
C7x CGT never was clickwrapped, as the arch is newer than those dark times :)
BTW, assuming that meta-arago is the only consumer of meta-ti components is not very safe.
Agreed. We are already toying around with supporting OpenBMC which absolutely does not use arago.
Heh, and I was referring to customers, OEMs and the community at large. :)
Quoted 39 lines
Quoted 39 lines
But I think dropping CGT for TMS740 and old CGT 7.x for C6x should be fine and those are the only remaining clickwrapped recipes.
IIRC, TMS740 arch was an old ARM MCU, so generic ARM CGT should probably also work, I guess.
Quoted 25 lines
Quoted 17 lines
Quoted 4 lines
Also, is this URI
functionality baked into the http fetcher or is this just leaning on bitbake being unable to resolve the domain and then falling back on the local copy?This is basic Bitbake fetcher functionality and is well documented. High level order of operations to locate sources:
1. Check if you already have them in your local
DL_DIR
2. Go through the list of configured PREMIRRORS to locate the sources there
3. Actually hit the upstreamSRC_URIand try to download the original src
4. If everything else fails, check through the list of "post" MIRRORSSo, requiring user to pre-download the sources manually and placing them in their local
DL_DIRper the original documentation would shortcut the process at step 1.Quoted 7 lines
Otherwise it would break at step 3 (and 4) and hopefully the weird URL would give user some clues or at least force to read the docs...
There's nothing special about the URL, besides the convention that .local is reserved - https://en.wikipedia.org/wiki/.local - and the entire name suggesting to install the sources in local dir :)
Quoted 5 lines
Ah, alright. At least this isn't that bad then. I still don't like the idea of being able to reach steps 3&4 in this case as it will check http sources. Local is reserved but it's still not a great idea to allow this fetch to go through, even if *ideally* it should fail to resolve.
You can try adding do_fetch[network] = "0" to that recipe...