The Yocto Project 3.0 release

We haven't solved that issue however it has turned out to be more of a theoretical problem than one which has effects in real world usage. Back in 2016 that wasn't clear but we've a few years of use to base that on now. There are ways of using the system you'd avoid the problem and ways you can have a large risk of exposure. It could be solved at a cost of much longer build times but we aren't seeing the evidence that shows it being an issue that justifies it. There are also protection mechanisms in place which also help avoid issues such as removal of sysroot artifacts where their hashes have changed. Those mechanisms came after the initial introduction of Recipe Specific Sysroots.