On Wed, Feb 26, 2025 at 10:15:50AM +0100, Patrick Steinhardt wrote: > > I'm hoping you can tell me I'm holding it wrong, and there's some way to > > do an incremental build when crossing these sorts of boundaries (without > > blowing away all of the build products). > > > > I do at least use ccache which makes the "rm -rf" case a little less > > painful. > > You're not holding it wrong. The problem is that this patch series > introduces a backwards-incompatible change to the "sane_tools_path" > option as it changes it from a string to an array, which makes Meson > hiccup. Once Meson is not considered to be experimental anymore we > should refrain from changing option types going forward, but until then > I consider it to be okayish to break things like this. > > From my point of view we can treat Meson as stable as soon as Git v2.49 > is out. So from thereon, I will make sure to not include backwards > incompatible changes anymore. Thanks. It's comforting to hear that this is something that's under our control. -Peff
