On Fri, Mar 04, 2022 at 03:16:31AM +0000, Alejandro Hernandez wrote:On 3/3/22 23:37, Denys Dmytriyenko wrote:On Thu, Mar 03, 2022 at 09:11:28PM +0000, Alejandro Hernandez Samaniego wrote:On 3/3/22 10:55, Abdellatif El Khlifi wrote:Hello, I suggest the following: In meta-arm-bsp/conf/layer.conf add : LAYERDEPENDS_meta-arm-bsp:append:qemuarm64-secureboot = " meta-python openembedded-layer"This statement is a little confusing (to me), please correct me if I'm wrong, but you're saying we should set a dependency from meta-arm-bsp layer, only for qemuarm64-secureboot, however, the qemuarm64-secureboot is part of meta-arm and not meta-arm-bsp, AFAIC meta-arm-bsp has now knowledge of its existence, in fact there's no other mention of qemuarm64-secureboot in meta-arm-bsp.Moreover, optee is used by other BSP layers (e.g. meta-ti) by depending on meta-arm, not meta-arm-bsp. Depending on python3-cryptography which is only available in meta-python (part of meta-openembedded) should be avoided. Back in the day we pushed for moving other python3 dependencies like pycryptodome and pyelftools into OE-Core: https://git.openembedded.org/meta-openembedded/commit/?id=a8f3c00d8d113b46a49584682e10435157d516ca https://git.yoctoproject.org/meta-arm/commit/?id=f2069723f27d9229e8ec74263a41160c8df32571 We could try doing the same with this new python3-cryptography dependecy and propose moving it to OE-Core. Alternatively, consider adding it to meta-arm? Not ideal, but meta-arm-bsp briefly carried alternative/older version recently: https://git.yoctoproject.org/meta-arm/commit/?id=a15c16068ab011e2ba91a6c4ca6e1251de0d8058I agree with Denys's point here, I think its likely there's other cases just like meta-ti, and we would be forcing a meta-oe and meta-python dependency on them, IMO it would make sense to add a copy of python3-cryptography to meta-arm (especially since there's been similar situations in the past) and in parallel try to make a case for python3-cryptography to be moved from meta-python to OE-core. Once (and if) we're successful we can delete the python3-cyrptography copy from meta-arm.This seems reasonable. Can you rework your series to add this? Also, we need to keep the older version of OPTEE for corstone1000 (for the kirkstone release). So, if you can keep that around in v2, it would be appreciated. Thanks, Jon
Will do, I'll send a v2 soon.
Cheers,
Alejandro
Alejandro
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#3142): https://lists.yoctoproject.org/g/meta-arm/message/3142 Mute This Topic: https://lists.yoctoproject.org/mt/89404067/4354175 Group Owner: meta-arm+owner@lists.yoctoproject.org Unsubscribe: https://lists.yoctoproject.org/g/meta-arm/unsub [alhe@linux.microsoft.com] -=-=-=-=-=-=-=-=-=-=-=-