It really depends on exactly what the problem scenario is. Currently, whenever *any* QML file changes, the whole cache is dropped and rebuilt. This includes SDK and base QML deps, not only files shipped by the app itself.
The only case where it is currently not rebuilt is when a provider library changes its QML bindings ABI. For this we are looking into ways to encode library versions on the magic headers of the cache file, although for now considering libraries are only updated on image upgrade, the cache should ensure validity. The only breaking case is when the developer pushes a new QML plugin with different ABI than what the cache was built against. So I guess the question is: What was the scenario/issue that happened which lead to this bug? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1444937 Title: QML cache gets stale too easily To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtdeclarative-opensource-src/+bug/1444937/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
