sthe challenge of managing C++ third-party library dependencies for the Nixl project—specifically asio and taskflow—when building a Python wheel without using git submodules (subprojects).

The current dependency approach utilizes pre-built RPMs containing the necessary C++ libraries. This works today but creates a high risk of version mismatch and significant manual maintenance. If the Nixl codebase updates its expected library versions, but the local build environment still uses older RPMs, an incompatible and incorrect Nixl wheel could be built and shipped.

The goal is to decide on a reliable strategy to track and validate C++ dependency versions to ensure the correct libraries are always used during the Nixl wheel build process.