John M. Harris Jr wrote:
However, I believe there's a third option here. It could be as
simple as
providing a python3-static in addition, and NOT using `alternatives`. This
way, packages and scripts that actually need the performance improvements
can directly call python3-static, and everything else just continues to
work as it does now.
But the wasted space will be even more, because now you have libpython, the
dynamic python3 linked against it, AND the python3-static binary. So it does
not address the issue at all.
Kevin Kofler