How can I separate the use of Meson and CMake on a Debian system when handling the Fossil Test dependency for unit testing?

[dreamer-coding]

The project primarily uses Meson for its build system (version 1.3.0 or newer), but conflicts arise because the system has an older version of CMake (3.13.4), which is only used for the CMake CI pipeline. How can I ensure that these two pipelines remain isolated without causing a domino effect of dependency conflicts? Ideally, the solution should maintain the integrity of both pipelines and prevent cross-contamination between Meson and CMake during CI execution.

Has anyone else hit this issue for a project that uses both Meson and CMake?

I had to use subproject to make it work but I can already see there is going to be a domino effect just from having to do that as I prefer not to change that for command-line applications when I eventually add CMake to them.

One of those silly projects: https://github.com/fossillogic/fossil-tofu