Re: [PATCH 3/3] meta-arago-test: opencl-headers version v2023.12.14->v2024.05.08

[Ryan Eatmon <reatmon@ti.com>]

On 2/5/2025 2:04 PM, a-christidis@ti.com wrote:
> From: Antonios Christidis <a0507488@uda0867391-2.dhcp.ti.com>
> 
> This version of the headers is required for OpenCl-CTS.
> 
> Carry this bbappend, as a version pump wasn't possible on the upstream meta-oe
> layer. As per the LTS process.
> 
> Signed-Off-By: Antonios Christidis <a-christidis@ti.com>
> ---
>   .../recipes-extended/opencl/opencl-headers_%.bbappend            | 1 +
>   1 file changed, 1 insertion(+)
>   create mode 100644 meta-arago-test/recipes-extended/opencl/opencl-headers_%.bbappend
> 
> diff --git a/meta-arago-test/recipes-extended/opencl/opencl-headers_%.bbappend b/meta-arago-test/recipes-extended/opencl/opencl-headers_%.bbappend
> new file mode 100644
> index 00000000..4dff02d9
> --- /dev/null
> +++ b/meta-arago-test/recipes-extended/opencl/opencl-headers_%.bbappend
> @@ -0,0 +1 @@
> +SRCREV = "8275634cf9ec31b6484c2e6be756237cb583999d"


This is problematic.

We are working to move at least meta-arago-test to be be yocto compliant 
and bare .bbappends that change things like this are considered bad form.

Here is an example of an upcoming patch that I will be sending to adress 
this same issue with the piglit package:

https://git.ti.com/cgit/arago-project/meta-arago/commit/?id=ecc08cf6204f9f935f39fe5308efbb537b99824e


Part of the log term plan has been to move meta-arago-test over to 
meta-ti-test in the meta-ti repo.  And that repository is yocto 
compliant and we want to always keep it.


-- 
Ryan Eatmon                reatmon@ti.com
-----------------------------------------
Texas Instruments, Inc.  -  LCPD  -  MGTS