01:44 <smurray> vd: as I mentioned, that's likely a question for RP. I'm guessing it's more involved, as it's effectively synchronizing two bitbake engine instances AIUI

07:18 <RP> vd: from bitbake's perspective, mc dependencies are hard and tricky to handle performance wise. Having them clear and separated makes them easier for bitbake and discourages users from adding lots of them. Yes, we probably could make it all appear the same to the user but I think you'd then soon be complaining about speed and other issues.

09:30 <banana_smoothie> Hello. I want to import a prebuilt third-party python package under dunfell release, but for some reason it doesn't allow it and returns with "No module found" error. Is there any special configuration in yocto to import a package from an external party?

16:06 <vd> RP: thank you. So given your input on bitbake's performance mc-wise, the best approach is to make image recipe able to choose a difference kernel provider, so that we can use linux-dummy from an image recipe to build a trivial container image

16:16 <RP> vd: no, you can't make an image recipe choose a provider