Package version 0.01: Built with libraries abc version 2, def version 0.1 and ghi version 7.2.2
Your system has requirements: abc version 2, def version 0.2 and ghi version 8.0.0
Package version 0.02: Requires abc version 3, def version 0.2 and ghi version 8.0.1
You realise that those differences in version would mean that you would have to basically recompile (then debug and recompile) your entire operating system with the three upgraded packages, and deal with a full cascade of dependencies, not just the package you really want to compile, OR basically sit down and rewrite Package 0.02 from the ground up using older libraries than it was originally written for.
You decide to make do with the old version of the package.
Package version 0.01: Built with libraries abc version 2, def version 0.1 and ghi version 7.2.2
Your system has requirements: abc version 2, def version 0.2 and ghi version 8.0.0
Package version 0.02: Requires abc version 3, def version 0.2 and ghi version 8.0.1
You realise that those differences in version would mean that you would have to basically recompile (then debug and recompile) your entire operating system with the three upgraded packages, and deal with a full cascade of dependencies, not just the package you really want to compile, OR basically sit down and rewrite Package 0.02 from the ground up using older libraries than it was originally written for.
You decide to make do with the old version of the package.
Can you not build it in a venv to not mess with your system packages?